Accessing and displaying information corresponding to past times and future times

ABSTRACT

The present disclosure relates to techniques accessing and displaying information pertaining to past times and future times. In some embodiments, a device displays a first current-time indicator and a user interface object configured to display information corresponding to a first information source and to the current time. In some embodiments, in response to and in accordance with detecting a rotation of a rotatable input mechanism, the device displays a non-current-time indicator indicating a non-current time, and updates the first user interface object to display information corresponding to the first information source and the non-current time. In some embodiments, the device continues to display an indication of the current time.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/171,999, entitled “Accessing and displayinginformation corresponding to past times and future times,” filed on Jun.5, 2015, and U.S. Provisional Patent Application No. 62/212,582,entitled “Accessing and displaying information corresponding to pasttimes and future times,” filed on Aug. 31, 2015, which are herebyincorporated by reference in their entirety.

This application relates to the following applications: U.S. ProvisionalApplication Ser. No. 62/032,562, filed Aug. 2, 2014; U.S. ProvisionalApplication Ser. No. 62/044,994, filed Sep. 2, 2014; InternationalPatent Application Serial No. PCT/US2013/040087, entitled “Device,Method, and Graphical User Interface for Moving a User Interface ObjectBased on an Intensity of a Press Input,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040072, entitled“Device, Method, and Graphical User Interface for Providing Feedback forChanging Activation States of a User Interface Object,” filed May 8,2013; International Patent Application Serial No. PCT/US2013/040070,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMay 8, 2013; International Patent Application Serial No.PCT/US2013/040067, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040061, entitled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040058, entitled “Device, Method, and Graphical UserInterface for Displaying Additional Information in Response to a UserContact,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040056, entitled “Device, Method, and Graphical UserInterface for Scrolling Nested Regions,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040054, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed May 8, 2013; International Patent ApplicationSerial No. PCT/US2013/069489, entitled “Device, Method, and GraphicalUser Interface for Switching Between User Interfaces,” filed Nov. 11,2013; International Patent Application Serial No. PCT/US2013/069486,entitled “Device, Method, and Graphical User Interface for DeterminingWhether to Scroll or Select Content,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069484, entitled “Device,Method, and Graphical User Interface for Moving a Cursor According to aChange in an Appearance of a Control Icon with SimulatedThree-Dimensional Characteristics,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069483, entitled “Device,Method, and Graphical User Interface for Transitioning Between TouchInput to Display Output Relationships,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069479, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069472, entitled“Device, Method, and Graphical User Interface for Navigating UserInterface Hierarchies,” filed Nov. 11, 2013; International PatentApplication Serial No. PCT/US2013/040108, entitled “Device, Method, andGraphical User Interface for Moving and Dropping a User InterfaceObject,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040101, entitled “Device, Method, and Graphical UserInterface for Selecting User Interface Objects,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040098, entitled“Device, Method, and Graphical User Interface for Displaying ContentAssociated with a Corresponding Affordance,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040093, entitled“Device, Method, and Graphical User Interface for Transitioning BetweenDisplay States in Response to a Gesture,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040053, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects,” filed May 8, 2013; U.S. Patent ApplicationSer. No. 61/778,211, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,191, entitled “Device, Method, and Graphical User Interface forDisplaying User Interface Objects Corresponding to an Application,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,171,entitled “Device, Method, and Graphical User Interface for DisplayingAdditional Information in Response to a User Contact,” filed Mar. 12,2013; U.S. Patent Application Ser. No. 61/778,179, entitled “Device,Method and Graphical User Interface for Scrolling Nested Regions,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,156, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed Mar. 12, 2013; U.S. Patent Application Ser.No. 61/778,125, entitled “Device, Method, And Graphical User Interfacefor Navigating User Interface Hierarchies,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/778,092, entitled “Device, Method, andGraphical User Interface for Selecting Object Within a Group ofObjects,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,418, entitled “Device, Method, and Graphical User Interface forSwitching Between User Interfaces,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,416, entitled “Device, Method, and GraphicalUser Interface for Determining Whether to Scroll or Select Content,”filed Mar. 13, 2013; U.S. Patent Application Ser. No. 61/747,278,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback,” filed Dec.29, 2012; U.S. Patent Application Ser. No. 61/778,414, entitled “Device,Method, and Graphical User Interface for Moving and Dropping a UserInterface Object,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,413, entitled “Device, Method, and Graphical User Interface forSelecting User Interface Objects,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,412, entitled “Device, Method, and GraphicalUser Interface for Displaying Content Associated with a CorrespondingAffordance,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,373, entitled “Device, Method, and Graphical User Interface forManaging Activation of a Control Based on Contact Intensity,” filed Mar.12, 2013; U.S. Patent Application Ser. No. 61/778,265, entitled “Device,Method, and Graphical User Interface for Transitioning Between DisplayStates in Response to a Gesture,” filed Mar. 12, 2013; U.S. PatentApplication Ser. No. 61/778,367, entitled “Device, Method, and GraphicalUser Interface for Moving a User Interface Object Based on an Intensityof a Press Input,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,363, entitled “Device, Method, and Graphical User Interface forTransitioning Between Touch Input to Display Output Relationships,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,287,entitled “Device, Method, and Graphical User Interface for ProvidingFeedback for Changing Activation States of a User Interface Object,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,284,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,239, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/688,227, entitled “Device, Method, andGraphical User Interface for Manipulating User Interface Objects withVisual and/or Haptic Feedback,” filed May 9, 2012; U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” and U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. Provisionalpatent application entitled “Reduced-Size Interfaces for ManagingAlerts”, filed on Sep. 2, 2014, naming Lawrence Yang et al. asinventors; U.S. Provisional patent application entitled “Stopwatch andTimer User Interfaces”, filed on Sep. 2, 2014, naming Eric Wilson et al.as inventors; U.S. Provisional Patent Application Ser. No. 62/026,532,“Raise Gesture Detection in a Device,” filed Jul. 18, 2014; U.S. patentapplication Ser. No. 14/476,700, “Crown Input for a Wearable ElectronicDevice,” filed Sep. 3, 2014; and U.S. New U.S. Provisional patentapplication “Obtaining and Displaying Time-Related Data On A SmartWatch,” filed Jun. 5, 2015, naming Eliza C. Block et al. as inventors.The content of these applications is hereby incorporated by reference intheir entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for accessing information thatcorresponds to a non-current time.

BACKGROUND

Users of portable electronic devices, including smart watches, requireaccess to information corresponding to past times, current times, andfuture times. Users require simpler and more intuitive ways to accesssuch past and future information, and to display past and futureinformation in a manner that clearly indicates the time to which theinformation corresponds.

BRIEF SUMMARY

Some techniques for accessing and presenting information correspondingto past times and future times in portable electronic devices arecumbersome and inefficient. For example, existing techniques require auser to execute several inputs and to navigate a complex series ofnested menus in order to access information corresponding to past timesand future times. Existing interfaces for viewing informationcorresponding to past times and future times require a user to enter aspecific application, such as a calendar application, a weatherapplication, or a stock-market application, before viewing pastinformation or future information. While some existing interfaces mayfacilitate the presentation of current information on home screens, lockscreens, and other summary interfaces, existing interfaces do notfacilitate accessing future and/or past information in the same format.Existing techniques are unintuitive and inefficient, requiring morecomplex and cumbersome inputs and more time than necessary, which wastesuser time and device energy. This latter consideration is particularlyimportant in battery-operated devices.

Accordingly, there is a need for portable electronic devices withfaster, more efficient, less cumbersome methods and interfaces foraccessing and presenting information corresponding to past times andfuture times. Specifically, there is a need for improved methods forpresenting information on an interface of a portable electronic device,wherein the information presented corresponds to a displayed non-current(past or future) time.

Such methods and interfaces optionally complement or replace othermethods for accessing and presenting information corresponding to pasttimes and future times. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface,including by providing an interactive interface that dynamically updatesuser interface objects to intuitively present temporally-relatedinformation for future times and past times. Such methods and interfacesmay further reduce the cognitive burden on a user and produce a moreefficient human-machine interface by allowing a user to recognizecorrelations and connections between otherwise disparate pieces ofinformation that are interrelated by way of their corresponding to thesame time in the future or the same time in the past. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges (and decrease thetime to fully charge a battery), including by reducing unnecessary oraccidental inputs and by obviating unnecessary extra user inputs.

Such methods and interfaces optionally complement or replace othermethods for accessing and presenting information corresponding to pasttimes and future times. Such methods and interfaces reduce number,extent and/or nature of the inputs from a user and produce a moreefficient human-machine interface, including by providing an interactiveinterface that dynamically updates user interface objects to intuitivelypresent temporally-related information for future times and past times.Such methods and interfaces may reduce the number of extraneous,repetitive, or unnecessary inputs required, thereby reducing processingpower, reducing battery usage, and/or reducing the amount of time forwhich a device must be used. For battery-operated computing devices,such methods and interfaces conserve power and increase the time betweenbattery charges (and decrease the time to fully charge a battery),including by reducing unnecessary or accidental inputs and by obviatingunnecessary extra user inputs.

The above deficiencies and other problems are reduced or eliminated bythe disclosed devices, methods, and computer-readable media. In someembodiments, the device is a desktop computer. In some embodiments, thedevice is portable (e.g., a notebook computer, tablet computer, orhandheld device). In some embodiments, the device has a touchpad. Insome embodiments, the device has a touch-sensitive display (also knownas a “touch screen” or “touch screen display”). In some embodiments, thedevice has hardware input mechanisms such as depressible buttons and/orrotatable input mechanisms. In some embodiments, the device has agraphical user interface (GUI), one or more processors, memory, and oneor more modules, programs, or sets of instructions stored in the memoryfor performing multiple functions. In some embodiments, the userinteracts with the GUI through finger contacts and gestures on thetouch-sensitive surface and/or through rotating the rotatable inputmechanism and/or through depressing hardware buttons. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer-readable storagemedium or other computer program product configured for execution by oneor more processors. Executable instructions for performing thesefunctions are, optionally, included in a transitory computer-readablestorage medium or other computer program product configured forexecution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a rotatable input mechanism. Insome embodiments, the method comprises displaying a first current-timeindicator indicating a current time; displaying a first user interfaceobject configured to display information corresponding to the currenttime, wherein the information corresponding to the current time pertainsto a first information source and is information other than a day, time,or date of the current time; and detecting a first rotation of therotatable input mechanism. In some embodiments, the method furthercomprises, in response to detecting the first rotation of the rotatableinput mechanism: displaying a non-current-time indicator indicating afirst non-current time determined in accordance with the first rotation;updating the first user interface object to display informationcorresponding to the first non-current time, wherein the informationcorresponding to the first non-current time pertains to the firstinformation source and is information other than a day, time, or date ofthe first non-current time; and displaying one of the first current-timeindicator and a second current-time indicator.

In accordance with some embodiments, a non-transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by a portable multifunctiondevice with a display and a rotatable input mechanism, cause the deviceto: display a first current-time indicator indicating a current time;display a first user interface object configured to display informationcorresponding to the current time, wherein the information correspondingto the current time pertains to a first information source and isinformation other than a day, time, or date of the current time; anddetect a first rotation of the rotatable input mechanism. In someembodiments, the instructions further cause the device to, in responseto detecting the first rotation of the rotatable input mechanism:display a non-current-time indicator indicating a first non-current timedetermined in accordance with the first rotation; update the first userinterface object to display information corresponding to the firstnon-current time, wherein the information corresponding to the firstnon-current time pertains to the first information source and isinformation other than a day, time, or date of the first non-currenttime; and display one of the first current-time indicator and a secondcurrent-time indicator.

In accordance with some embodiments, a transitory computer readablestorage medium stores one or more programs, the one or more programscomprising instructions, which when executed by a portable multifunctiondevice with a display and a rotatable input mechanism, cause the deviceto: display a first current-time indicator indicating a current time;display a first user interface object configured to display informationcorresponding to the current time, wherein the information correspondingto the current time pertains to a first information source and isinformation other than a day, time, or date of the current time; anddetect a first rotation of the rotatable input mechanism. In someembodiments, the instructions further cause the device to, in responseto detecting the first rotation of the rotatable input mechanism:display a non-current-time indicator indicating a first non-current timedetermined in accordance with the first rotation; update the first userinterface object to display information corresponding to the firstnon-current time, wherein the information corresponding to the firstnon-current time pertains to the first information source and isinformation other than a day, time, or date of the first non-currenttime; and display one of the first current-time indicator and a secondcurrent-time indicator.

In accordance with some embodiments, a device comprises a display; arotatable input mechanism; one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe device to: display a first current-time indicator indicating acurrent time; display a first user interface object configured todisplay information corresponding to the current time, wherein theinformation corresponding to the current time pertains to a firstinformation source and is information other than a day, time, or date ofthe current time; and detect a first rotation of the rotatable inputmechanism. In some embodiments, the instructions, when executed by theone or more processors, can optionally further cause the device to, inresponse to detecting the first rotation of the rotatable inputmechanism: display a non-current-time indicator indicating a firstnon-current time determined in accordance with the first rotation;update the first user interface object to display informationcorresponding to the first non-current time, wherein the informationcorresponding to the first non-current time pertains to the firstinformation source and is information other than a day, time, or date ofthe first non-current time; and display one of the first current-timeindicator and a second current-time indicator.

In accordance with some embodiments, a device comprises: means fordisplaying a first current-time indicator indicating a current time;means for displaying a first user interface object configured to displayinformation corresponding to the current time, wherein the informationcorresponding to the current time pertains to a first information sourceand is information other than a day, time, or date of the current time;means for detecting a first rotation of a rotatable input mechanism;means for, in response to detecting the first rotation of the rotatableinput mechanism: displaying a non-current-time indicator indicating afirst non-current time determined in accordance with the first rotation;updating the first user interface object to display informationcorresponding to the first non-current time, wherein the informationcorresponding to the first non-current time pertains to the firstinformation source and is information other than a day, time, or date ofthe first non-current time; and displaying one of the first current-timeindicator and a second current-time indicator.

In accordance with some embodiments, an electronic device comprises adisplay unit; a rotatable input mechanism unit; and a processing unitcoupled to the display unit and the rotatable input mechanism unitconfigured to: enable display on the display unit of a firstcurrent-time indicator indicating a current time; enable display on thedisplay unit of a first user interface object configured to displayinformation corresponding to the current time, wherein the informationcorresponding to the current time pertains to a first information sourceand is information other than a day, time, or date of the current time;detect a first rotation of the rotatable input mechanism unit; inresponse to detecting the first rotation of the rotatable inputmechanism unit: enable display on the display unit of a non-current-timeindicator indicating a first non-current time determined in accordancewith the first rotation; update the first user interface object todisplay information corresponding to the first non-current time, whereinthe information corresponding to the first non-current time pertains tothe first information source and is information other than a day, time,or date of the first non-current time; and enable display on the displayunit of one of the first current-time indicator and a secondcurrent-time indicator.

Thus, devices are provided with faster, more efficient, less cumbersomemethods and interfaces for accessing and presenting informationcorresponding to past times and future times; these devices, methods,and interfaces thereby increase the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces canoptionally complement or replace other methods for accessing andpresenting information corresponding to past times and future times.

DESCRIPTION OF THE FIGURES

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIGS. 4A and 4B illustrate an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 5A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display and a rotatable and depressible inputmechanism in accordance with some embodiments.

FIG. 5B illustrates a portable multifunction device having atouch-sensitive display and a rotatable and depressible input mechanismin accordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A and 6B illustrate exemplary context-specific user interfaces.

FIGS. 7A and 7B illustrate exemplary context-specific user interfaces.

FIG. 8 illustrates exemplary context-specific user interfaces.

FIG. 9 illustrates exemplary context-specific user interfaces.

FIG. 10 illustrates exemplary context-specific user interfaces.

FIGS. 11A-11C illustrate exemplary context-specific user interfaces.

FIG. 12 illustrates exemplary context-specific user interfaces.

FIGS. 13A and 13B illustrate exemplary context-specific user interfaces.

FIG. 14A illustrates exemplary context-specific user interfaces.

FIGS. 14B-14T illustrate exemplary context-specific user interfaces.

FIG. 15 illustrates exemplary context-specific user interfaces.

FIGS. 16A-16C illustrate exemplary context-specific user interfaces.

FIGS. 17A and 17B illustrate exemplary context-specific user interfaces.

FIGS. 18A-18C illustrate exemplary context-specific user interfaces.

FIG. 19 illustrates exemplary context-specific user interfaces.

FIG. 20 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 21 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 22 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 23 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 24 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 25 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 26 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27A is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27B is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27C is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27D is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27E is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27F is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 28 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 29 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 30 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 31 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 32 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 33 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 34 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 35 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 36 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 37 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 38 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 39 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 40 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 41 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 42 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 43 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 44 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 45 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 46 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 47 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 48 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 49 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 50 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 51 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 52 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 53A-53F illustrate exemplary user interfaces in accordance withsome embodiments.

FIGS. 54A-54E are flow diagrams illustrating methods of activating amode of operation in accordance with some embodiments.

FIG. 55 is a functional block diagram of an electronic device inaccordance with some embodiments.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for accessing and presenting information corresponding topast times and future times. The embodiments described herein improve oncurrent methods by allowing for efficient, convenient, fast, andintuitive ways of accessing and presenting information corresponding topast times and future times. Such techniques can reduce the cognitiveburden on a user who accesses information corresponding to past timesand future times, thereby enhancing productivity. Further, suchtechniques can reduce processor and battery power otherwise wasted onredundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for accessing and presenting information correspondingto past times and future times. FIGS. 53A-F illustrate exemplary userinterfaces in accordance with some embodiments. The user interfaces inthe figures are also used to illustrate the processes described below,including the processes in FIGS. 54A-E.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for providingcontext-specific user interfaces. FIGS. 6-19 illustrate exemplarycontext-specific user interfaces. The user interfaces in the figures arealso used to illustrate the processes described below, including theprocesses in FIGS. 20-33.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” can optionally be construed to mean “when” or “upon” or“in response to determining” or “in response to detecting,” depending onthe context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” can optionally be construed tomean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device can optionally support a variety of applications, such as oneor more of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 can optionally include one or more computer-readable storagemediums. The computer-readable storage mediums can optionally betangible and non-transitory. Memory 102 can optionally includehigh-speed random access memory and can optionally also includenon-volatile memory, such as one or more magnetic disk storage devices,flash memory devices, or other non-volatile solid-state memory devices.Memory controller 122 can optionally control access to memory 102 byother components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 can optionally beimplemented on a single chip, such as chip 104. In some otherembodiments, they can optionally be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data can optionally beretrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button can optionally disengage a lock oftouch screen 112 or begin a process that uses gestures on the touchscreen to unlock the device, as described in U.S. patent applicationSer. No. 11/322,549, “Unlocking a Device by Performing Gestures on anUnlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which ishereby incorporated by reference in its entirety. A longer press of thepush button (e.g., 206) can optionally turn power to device 100 on oroff. The user can optionally customize a functionality of one or more ofthe buttons. Touch screen 112 is used to implement virtual or softbuttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output can optionallyinclude graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output can optionally correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 can optionally use LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiescan optionally be used in other embodiments. Touch screen 112 anddisplay controller 156 can optionally detect contact and any movement orbreaking thereof using any of a plurality of touch sensing technologiesnow known or later developed, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with touch screen 112. In an exemplaryembodiment, projected mutual capacitance sensing technology is used,such as that found in the iPhone® and iPod Touch® from Apple Inc. ofCupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 can optionally have a video resolution in excess of 100dpi. In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user can optionally make contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100 canoptionally include a touchpad (not shown) for activating or deactivatingparticular functions. In some embodiments, the touchpad is atouch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad can optionally be atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 can optionally include a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 can optionally also include one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 can optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 can optionallycapture still images or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch screen display 112 onthe front of the device so that the touch screen display can optionallybe used as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image can optionally be obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 can optionally be used along with the touch screendisplay for both video conferencing and still and/or video imageacquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 can optionally also include one or more proximity sensors166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface118. Alternately, proximity sensor 166 can optionally be coupled toinput controller 160 in I/O subsystem 106. Proximity sensor 166 canoptionally perform as described in U.S. patent application Ser. No.11/241,839, “Proximity Detector In Handheld Device”; Ser. No.11/240,788, “Proximity Detector In Handheld Device”; Ser. No.11/620,702, “Using Ambient Light Sensor To Augment Proximity SensorOutput”; Ser. No. 11/586,862, “Automated Response To And Sensing Of UserActivity In Portable Devices”; and Ser. No. 11/638,251, “Methods AndSystems For Automatic Configuration Of Peripherals,” which are herebyincorporated by reference in their entirety. In some embodiments, theproximity sensor turns off and disables touch screen 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 can optionally also include one or more accelerometers 168.FIG. 1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 can optionally be coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 can optionallyperform as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which can optionally be a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 can optionally include the following modules (or setsof instructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which can optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that can optionally be stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 can optionally be used to manage an addressbook or contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 can optionally be used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication can optionally use any of a pluralityof communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages can optionally include graphics, photos, audio files,video files and/or other attachments as are supported in an MMS and/oran Enhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that can optionally be downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150can optionally be used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154can optionally be used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules can optionally be combined orotherwise rearranged in various embodiments. For example, video playermodule can optionally be combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 can optionally store a subset of the modules anddata structures identified above. Furthermore, memory 102 can optionallystore additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 can optionally be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected can optionally correspond to programmaticlevels within a programmatic or view hierarchy of the application. Forexample, the lowest level view in which a touch is detected canoptionally be called the hit view, and the set of events that arerecognized as proper inputs can optionally be determined based, at leastin part, on the hit view of the initial touch that begins a touch-basedgesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 can optionally utilize or call dataupdater 176, object updater 177, or GUI updater 178 to update theapplication internal state 192. Alternatively, one or more of theapplication views 191 include one or more respective event handlers 190.Also, in some embodiments, one or more of data updater 176, objectupdater 177, and GUI updater 178 are included in a respectiveapplication view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which can optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation can optionally also include speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers can optionally interact, or are enabled to interact, withone another. In some embodiments, metadata 183 includes configurableproperties, flags, and/or lists that indicate whether sub-events aredelivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 can optionally also include one or more physical buttons,such as “home” or menu button 204. As described previously, menu button204 can optionally be used to navigate to any application 136 in a setof applications that can optionally be executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 can optionally be storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules can optionally be combined or otherwiserearranged in various embodiments. In some embodiments, memory 370 canoptionally store a subset of the modules and data structures identifiedabove. Furthermore, memory 370 can optionally store additional modulesand data structures not described above.

Attention is now directed towards embodiments of user interfaces thatcan optionally be implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces can optionally be implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:    -   Icon 416 for telephone module 138, labeled “Phone,” which        optionally includes an indicator 414 of the number of missed        calls or voicemail messages;    -   Icon 418 for e-mail client module 140, labeled “Mail,” which        optionally includes an indicator 410 of the number of unread        e-mails;    -   Icon 420 for browser module 147, labeled “Browser;” and    -   Icon 422 for video and music player module 152, also referred to        as iPod (trademark of Apple Inc.) module 152, labeled “iPod;”        and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides        -   access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 can optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) canoptionally have one or more intensity sensors for detecting intensity ofcontacts (e.g., touches) being applied. The one or more intensitysensors of touch screen 504 (or the touch-sensitive surface) can provideoutput data that represents the intensity of touches. The user interfaceof device 500 can respond to touches based on their intensity, meaningthat touches of different intensities can invoke different userinterface operations on device 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, published as WIPO Publication No.WO/2013/169849, and International Patent Application Serial No.PCT/US2013/069483, titled “Device, Method, and Graphical User Interfacefor Transitioning Between Touch Input to Display Output Relationships,”filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276,each of which is hereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms can optionally permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 can optionally be a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 508can optionally be a button, in some examples.

Input mechanism 508 can optionally be a microphone, in some examples.Personal electronic device 500 can include various sensors, such as GPSsensor 532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 2000-3300 (FIGS. 20-33).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that can optionally be displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). Forexample, an image (e.g., icon), a button, and text (e.g., hyperlink) canoptionally each constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds canoptionally include a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A. (Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface can optionally receive a continuous swipecontact transitioning from a start location and reaching an endlocation, at which point the intensity of the contact increases. In thisexample, the characteristic intensity of the contact at the end locationcan optionally be based on only a portion of the continuous swipecontact, and not the entire swipe contact (e.g., only the portion of theswipe contact at the end location). In some embodiments, a smoothingalgorithm can optionally be applied to the intensities of the swipecontact prior to determining the characteristic intensity of thecontact. For example, the smoothing algorithm optionally includes one ormore of: an unweighted sliding-average smoothing algorithm, a triangularsmoothing algorithm, a median filter smoothing algorithm, and/or anexponential smoothing algorithm. In some circumstances, these smoothingalgorithms eliminate narrow spikes or dips in the intensities of theswipe contact for purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface can optionallybe characterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the term “open application” or “executing application”refers to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application can optionally be any oneof the following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

1. Context-Specific User Interfaces

Attention is now directed towards embodiments of context-specific userinterfaces (“UI”) and associated processes that may be implemented on amultifunction device with a display and a touch-sensitive surface, suchas devices 100, 300, and/or 500 (FIGS. 1A, 3A, and/or 5A).

The following examples illustrate exemplary embodiments ofcontext-specific user interfaces. Described herein are overall conceptsrelated to customizable context-specific user interfaces. It is notedthat the context-specific user interfaces described herein are editablein a number of ways. A user interface may display or otherwise indicatevarious types of information related to time, and the type(s) ofinformation may be customizable by the user. A user interface mayinclude aspects such as colors, density of display, and complications(or lack of complications) that are also customizable. As used here,consistent with its accepted meaning in art, a complication refers toany clock face feature other than those used to indicate the hours andminutes of a time (e.g., clock hands or hour/minute indications).Complications may provide different types of information to a user, suchas data obtained from an application, and the information conveyed to auser by a complication is also customizable, as described below.

These combinatorial features result in many thousands, if not more, ofavailable context-specific user interfaces. Since describing each ofthese permutations is not practical, particular aspects are highlightedwith particular context-specific user interfaces, but these exemplarydescriptions are in no way intended to limit such aspects to suchcontext-specific user interfaces, as specific aspects may be used inother context-specific user interfaces, and specific context-specificuser interfaces may have other aspects. These embodiments are meant toillustrate the overall concepts presented, but a skilled artisan willrecognize that numerous other embodiments are possible within the scopeof the techniques described herein.

FIG. 6A shows an exemplary context-specific user interface that may beoperated on device 600. Device 600 may be device 100, 300, or 500 insome embodiments. The electronic device has a display (e.g., 504).

A user keeping track of the time of day may wish to gain some sense ofhow much time has elapsed since a particular event. For example, a usermay wish to know how much time has elapsed since the last time the userviewed the time, or how much time has elapsed since a particular time ofday, like morning. In addition to viewing a clock face, the user maywish to receive additional visual cues that reinforce the perception ofelapsed time.

As shown in FIG. 6A, the device receives data representing user input602. In response to receiving the data, the device displays userinterface screen 604 on the display. Screen 604 includes clock face 606.In the example illustrated in FIG. 6A, the time is currently 7:00. Clockface 606 initially indicates a first time (10:05 as shown in FIG. 6A)that precedes the current time. Device 600 updates screen 604 byanimating the clock face to transition from indicating the first time toindicating the current time. Updated screen 604 is depicted as screen610, which displays clock face 612. Clock face 612 has been updated toindicate the current time. The animation from screens 604 to 610represents the passage of time from the first time to the current time.In some embodiments, screen 604 and/or 610 may also include anindication of the date.

As described above, the context-specific user interface exemplified inFIG. 6A first displays the clock face indicating a first time. The firsttime may be determined based on different criteria. In some embodiments,the device receives second data representing a time of a previous usermovement of the electronic device (e.g., a movement of the device suchas a lowering of the user's wrist, if the device is wearable, or othermovement indicative that the user is no longer actively viewing thedisplay). The time of the previous user movement of the device may bethe last time the user looked at the device, or the last time thedisplay of the device was turned off, prior to receiving the datarepresenting user input 602. The time of the previous user movement ofthe electronic device is then shown as the first time indicated by theclock face. For example, in FIG. 6A, 10:05 depicted by clock face 606may be the time of a previous user movement of the device, indicatingthe time of a previous user interaction. In these examples, when theuser interface screen updates, it provides the user an indication of howmuch time has elapsed since the previous user interaction (e.g., thelast time the user looked at device 600).

In other embodiments, the first time may be based on a predeterminedinterval of time. For example, the first time may precede the currenttime by a first duration, and the first duration may be a predeterminedduration before the current time. That is to say, rather than beingbased on a user interaction, the first time indicated by the clock facemay be based on a predetermined or fixed duration before the currenttime.

In some embodiments, the predetermined duration is 5 hours. In responseto user input, the clock face may depict a time 5 hours before thecurrent time, then animate the clock face to transition from indicatingthe first time to indicating the current time. For example, if thecurrent time is 6:00, the device may, in response to user input, displaya clock face showing 1:00 that is animated to transition from 1:00 to6:00.

In other embodiments, the first time may be based on a predeterminedtime of day. In this case, the device may begin the animation byindicating the same time of day (i.e., the first time) no matter thecurrent time, and then animate the clock face until it reaches thecurrent time. For example, the first time may be morning (e.g., 8:00am). In this example, if the current time is 6:00, the device may, inresponse to user input, display a clock face showing 8:00 that isanimated to transition from 8:00 to 6:00.

Regardless of how the first time is determined, in some embodiments, theclock face may be animated for a period of time indicative of theduration between the first time and the current time. That is to say,the length of the animation may be roughly proportional to the length ofthis duration. The length of animation may not be precisely proportionalto the first duration, but rather it may convey to the user a generalindication of an approximate length of the time. To illustrate using theexamples described above, the clock face may be animated for a longerperiod of time if transitioning from 8:00 to 6:00 than it is iftransitioning from 3:00 to 6:00. This may be particularly useful if theduration is variable, such as if the duration is based on the timebetween user interactions. In this case, a user will immediatelycomprehend that the time elapsed between interactions is longer if theanimation of the clock face is longer, or that the time betweeninteractions is shorter if the animation of the clock face is shorter.

In other embodiments, the clock face is animated for a period of timeindependent of the first duration. That is to say, the length of theanimation is not proportional to the duration between the first time andthe current time. In some embodiments, the length of animation may bethe same for each animation. To illustrate using the examples describedabove, the clock face may be animated for the same period of timeregardless if transitioning from 8:00 to 6:00 or from 3:00 to 6:00. Thismay be helpful to reduce the time a user is viewing the transition.Alternatively, the clock face is animated for a different period of timeif transitioning from 8:00 to 6:00 compared to transitioning from 3:00to 6:00, but the periods of time may not related to the first duration.

FIG. 6B illustrates optional features of this context-specific userinterface. In response to data representing user input 620, device 600displays user interface screen 622, which includes clock face 624. Inthis example, the current time is 10:25. Clock face 624 indicates afirst time (in this example, 10:05). As a background, clock face 624also displays an image of a mountain scene that is representative of thefirst time. For example, as shown in FIG. 6B, clock face 624 shows amorning view of the mountain scene (see, e.g., the position of sun 626in the sky). Therefore, a user viewing clock face 624 understands thetime based on the clock face itself and the background, which alsorepresents the time indicated by the clock face. Note that this providesadditional information to the user because the user understands that theindicated time is 10:05 am, not 10:05 pm, by the display of the scene.

In some embodiments, the device accesses an image of a scene that isrepresentative of the time indicated by the clock face. An image of ascene that is representative of a time may connote to the user a similartime of day, in conjunction with the time indicated by the clock face.The image of the scene need not connote the precise time indicated bythe clock face, nor does it need to be strictly linked to the time ofday at the location of the scene (this will be discussed in greaterdetail below). In some embodiments, the image of the scene is an imagecaptured at substantially the same time of day as the current time(i.e., the time of day when the image was taken at the scene). In otherembodiments, the image of the scene is an image captured at a differenttime of day, as compared to the current time.

In some embodiments, the image of the scene may depict, for example, acity, beach, desert, park, lake, mountain, or valley. In someembodiments, the scene may be recognizable to the user, such as a sceneof Yosemite Valley or Big Ben.

Device 600 then displays screens 630 and 640. Screen 630 is optional, asdescribed below, and includes clock face 632, which is indicating a timebetween the first time and the current time. This intermediate time isfurther represented on clock face 632 by the background (see, e.g.,setting sun 634). Screen 640 includes clock face 642, which depicts thecurrent time. Clock face 642 also displays a background that representsthe current time (see, e.g., moon 644).

Therefore, in some embodiments, and in response to receiving datarepresenting user input 620, the device accesses a first image of ascene representative of the first time (e.g., the background of clockface 624), accesses a second image of the scene representative of thecurrent time (e.g., the background of clock face 642), and in responseto receiving the data representing the user input, successively displaysthe first image of the scene and the second image of the scene.

The successive display indicates the passage of time from the first timeto the current time. The device may include a series of images for aparticular scene (e.g., time lapse images), each depicting a differenttime of day, such that any first time or current time depicted by theclock face has a corresponding image of the scene that is representativeof the depicted time. In some embodiments, the first image of the sceneand the second image of the scene are displayed as backgrounds on theuser interface screen.

In some embodiments, the device accesses a sequence of images of a scenethat includes a first image of the scene representative of the firsttime (e.g., the background of clock face 624), one or more second imagesof the scene representative of one or more times between the first timeand the current time (e.g., the background of clock face 632), and athird image of the scene representative of the current time (e.g., thebackground of clock face 642). In response to receiving the datarepresenting user input 620, the device displays the sequence of imagesof the scene by animating the sequence of images to indicate the passageof time from the first time to the current time (e.g., like a flipbook).In some embodiments, the scene is user-designated (e.g., the device maystore a set of time lapse images for different scenes, and the user mayselect the scene to be displayed).

As shown in FIG. 6B, device 600 sequentially displays screens 622, 630,and 640 to animate the displayed, respective backgrounds, therebyanimating the image of the scene like a flipbook to indicate the passageof time. In some embodiments, the transition from screen 620 to 630 to640 may also be animated, e.g., by animating the hands of the clock faceto rotate in a clockwise manner, and/or by animating the display of theimages of the scene, as with a flipbook. If the clock face instead oradditionally depicts a representation of a digital clock, the numericalindications of the hour and the minute may be animated in some fashionto depict the passage of time. By displaying both the animated clockface and the animated image(s) of the scene, the device provides theuser a clearer and readily distinguishable indication of the timebetween the first time and the current time.

In some embodiments, device 600 has a location sensor (e.g., GPS sensor532 and/or GPS module 135), and the device obtains a current location ofthe device from the location sensor. The first image of the scenerepresents the first time at the current location, and the second imageor the third image of the scene (e.g., whichever is representative ofthe current time) represents the current time at the current location.That is to say, the indicated passage of time reflects day/night hoursat the current location. For example, if the user is at a location nearthe Arctic Circle, the current day may have daytime hours close to 24hours (e.g., midnight sun). In this example, the images indicating thefirst time and the current time may all be daytime images of the scene(e.g., Yosemite Valley), even if the first time and the current time areseparated by a long period of time. Therefore, the images of the scenemay be representative of the depicted time(s) at the current location,but they may not be representative of the depicted time(s) at thelocation of the scene. This concept allows the device to display acontext-specific user interface for depicting the passage of time at thecurrent location and enhances a user's interaction with the device,since the animation is grounded in the user's experience (e.g.,perception of time) at the current location.

In some embodiments, the device displays a user interface object on theuser interface screen at a first position based on the first time. Insome embodiments, the position may be based on a position along theclock face, like an hour indication (e.g., 6 o'clock position at thelower center of the display). In some embodiments, the position may bebased on a position across a horizon, such as a position of the Sun orthe Moon. For example, in FIG. 6B, the position of sun 626 indicates thefirst time because it represents the sun in the scene at a position inthe east just short of high noon.

In some embodiments, the device animates the user interface object bymoving the user interface object from the first position to a secondposition on the user interface screen, where the second position isbased on the current time. Moving the user interface object from thefirst position to a second position indicates the passage of time fromthe first time to the current time. As shown in FIG. 6B, sun 626 movesacross the sky in the sequence of images of the scene (cf. sun 626 andsun 634). The user interface object then depicts moon 644 at a positionin the night sky indicating the current time. In some embodiments, theuser interface object is a graphical representation of a sun (e.g., 626and 634). In some embodiments, the user interface object is a graphicalrepresentation of a moon (e.g., 644).

In any of the embodiments described above, the user input may include amovement of the device. For example, a movement of the device could beraising of the user's wrist (if the device is wearable), or othermovement indicative of the user raising the device to view the display.These movements could be detected, for example, by using anaccelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor(e.g., 538), and/or a combination thereof. In any of thecontext-dependent faces described herein, a movement of the device maybe a user input that activates the display.

Further, in any of the context-dependent faces described herein, amovement of the device such as a lowering of the user's wrist (if thedevice is wearable) or other movement indicative that the user is nolonger actively viewing the display, or a lack of a movement of thedevice such as raising of the user's wrist (if the device is wearable)or other movement indicative of the user raising the device to view thedisplay, may be a user input that causes the device to turn off thedisplay.

In other embodiments, the device may have a touch-sensitive display ortouch-sensitive surface (e.g., touchpad 355 in FIG. 3, touch-sensitivesurface 451 in FIG. 4B, and/or touchscreen 504), and the user input maybe a contact on the touch-sensitive display.

Attention is now directed to the context-specific user interface shownin FIG. 7A. FIG. 7A shows exemplary context-specific user interfacesthat may be operated on device 700. Device 700 may be device 100, 300,or 500 in some embodiments. The electronic device has a touch-sensitivedisplay (e.g., touchscreen 504).

A user may wish to keep track of the time of day while also accessing astopwatch function. For example, in contexts such as running or cycling,a user may wish to operate a stopwatch, record laps, and still maintaina view of the time of day.

As shown in FIG. 7A, device 700 displays a clock face that indicatescurrent time, as depicted on user interface screen 702, on thetouch-sensitive display. The clock face includes hour hand and minutehand 704. The clock face also includes one or more indications of anhourly timescale (e.g., numbers 12, 1, 2, 3, and/or tick marks or othervisual indicators displayed at the corresponding positions on the clockface), such as 12 o'clock indicator 706. The clock face further includesstopwatch hand 708 (which, in some embodiments described below, alsoserves as a seconds hand. Note that, as used herein, the term secondshand refers to a hand on a clock face that indicates seconds, not asecond hand of two hands on a clock face).

As exemplified in FIG. 7A, device 700 receives user input, which in thiscase is touch 712 on start affordance 710. In response, the devicereplaces the 12 o'clock indicator 706 with stopwatch timescale indicator724, as shown on screen 720. Stopwatch indicator 724 shows that thestopwatch timescale is a 60 second timescale. A timescale for thestopwatch hand may refer to the amount of time needed for the stopwatchhand to complete one full revolution around the displayed clock face.Note that the clock face on screen 720 includes hour hand and minutehand 722 and stopwatch hand 726, which are the same as hour hand andminute hand 704 and stopwatch hand 708.

Further in response to touch 712, device 700 animates stopwatch hand 726to reflect passage of time, as shown by comparing screen 720 and 730. Asshown on screen 730, the stopwatch hand has moved to a second positionon the clock face (note the position of stopwatch hand 736), indicatingthe passage of time. Given that indicator 734 shows that the stopwatchtimescale is 60 seconds, the position of stopwatch hand 736 indicatesthat 25 seconds have passed. As shown in FIG. 7A, the user accesses thisinformation by touch 740 on lap affordance 738, which causes the displayof time 742, indicating the time elapsed since touch 712. Note that hourhand and minute hand 732 are the same as 722 and 704, and these twohands have not changed position in the last 25 seconds. In this example,the hour hand and minute hand are indicating the same time of day (e.g.,10:10) throughout screens 702, 720, and 730.

Stated another way, the device displays the time of day with the hourhand and the minute hand, and it additionally displays a stopwatch hand.In response to receiving data representing user input, the indication(s)of the hour are replaced with indication(s) of a first timescale of thestopwatch hand, but the hour hand and the minute hand continue toindicate the time of day, even though the hour indication(s) have beenreplaced. This allows the user to view a stopwatch and the time of daysimultaneously, while showing that the stopwatch has started andindicating the timescale for the stopwatch. Also in response toreceiving the data, the device animates the stopwatch hand to reflectpassage of time.

In some embodiments, while animating the stopwatch hand to reflect thepassage of time, the device receives second data representing a seconduser input, and in response to receiving the second data, the device maycease the animation of the stopwatch hand. For example, this mayfunction similar to a “stop” function for the stopwatch.

In some embodiments, the device may display on the touch-sensitivedisplay a first affordance representing a start/stop function (e.g.,affordance 710). The first data representing the first user input (e.g.,touch 712) and the second data representing the second user input bothrepresent contacts on the displayed first affordance. In otherembodiments, the device may display separate affordances for thestopwatch start and stopwatch stop functions.

In some embodiments, the device may display on the touch-sensitivedisplay a second affordance representing a lap function (e.g.,affordance 738). The devices receives third data representing a contacton the displayed second affordance after receiving the first data (e.g.,after invoking the start function) and before receiving the second data(e.g., before invoking the stop function). In response to receiving thethird data, the device displays a third numerical indication of elapsedtime between receiving the first data and receiving the third data. Forexample, this may function similar to a “lap” function for the stopwatchthat causes a display of the time elapsed since invoking the startfunction. As described above, this feature is illustrated on screen 730.

In some embodiments, the device may display on the touch-sensitivedisplay a third affordance representing a stopwatch application, whichis depicted as affordance 714 on screen 702. The device receives fourthdata representing a contact on the displayed third affordance, and inresponse to receiving the fourth data, the device launches the stopwatchapplication. This allows the user to access additional informationand/or functionality related to the stopwatch feature directly from thiscontext-specific user interface. In one embodiment, the stopwatchapplication is an application as described in related application: U.S.Provisional patent application entitled “Stopwatch and Timer UserInterfaces”, filed on Sep. 2, 2014, naming Eric Wilson et al. asinventors.

In some embodiments, the first timescale for the stopwatch hand may be60 seconds, 30 seconds, 6 seconds, or 3 seconds. In some embodiments,the movement of the stopwatch hand is animated at a rate based on thefirst timescale for the stopwatch hand. For example, the stopwatch handmay move faster if the timescale is 3 seconds than if the timescale is60 seconds. This allows the stopwatch hand to complete a full revolutionaround the clock face in the amount of time depicted by the firsttimescale.

In some embodiments, the device may substitute the one or moreindications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand by removing the one or more indicationsof the hourly timescale, displaying the indication of the firsttimescale for the stopwatch hand, and translating the displayedindication of the first timescale for the stopwatch hand in a rotationalmotion in a clockwise direction. As an illustrative example, if thedisplay includes 12 numerical indications of hourly timescale, and thefirst timescale for the stopwatch hand is a 6 second timescale, thedevice may substitute the 12 numerals with a single 6 numeral. In someembodiments, this may be the same 6 numeral that was previously theindicator for the 6 o'clock hour, such that the substitute and displayare not perceptible to the user. The device may display the 6 numericalindicating the first timescale for the stopwatch hand at the 6 o'clockposition on the clock face, then translate the 6 in a clockwise motionaround the clock face until it arrives at the top of the clock face(formerly the 12 o'clock position), at which point the translationstops. This improves the context-specific interface by reinforcing tothe user that the clock face has transitioned from indicating hours andminutes to indicating the first timescale for the stopwatch hand.

As illustrated in FIG. 7B, in some embodiments, the device has arotatable input mechanism (e.g., 506), which may be used as an optionalinput to change the stopwatch timescale. FIG. 7B shows screen 750 withclock face 752, which includes hour hand and minute hand 754, andstopwatch timescale indicator 756 (showing a 60 second timescale). Inresponse to receiving fifth data representing movement of the rotatableinput mechanism (e.g., movement 758), the device 700 changes thestopwatch timescale to a second timescale, as shown by stopwatchtimescale indicator 776, part of clock face 772 on screen 770. Note thatscreen 770 continues to display hour hand and minute hand 774. Thesecond stopwatch timescale is different from the first stopwatchtimescale. This allows the user to customize the timescale for thestopwatch hand through rotating the rotatable input mechanism, allowingfor a context-specific user interface depending on the user's desiredstopwatch timescale.

In some embodiments, the device substitutes the indication of the firsttimescale for the stopwatch hand with the indication of the secondtimescale for the stopwatch hand by removing the indication of the firsttimescale for the stopwatch hand, displaying the indication of thesecond timescale for the stopwatch hand, and translating the displayedindication of the second timescale for the stopwatch hand in arotational motion in a clockwise direction.

As shown in FIG. 7B, indicator of the second timescale for the stopwatchhand 760 is displayed at a position on the clock face that indicates itsrelative position in the first timescale For example, indicator of a 30second timescale 760 is displayed on clock face 752 at a position basedon the sixty second timescale indicated by 756. In response to receivingdata representing movement 758, the device removes 756, displays 760,and translates 760 in a rotational motion in a clockwise direction untilit reaches the former position of the indicator of the first timescalefor the stopwatch hand (e.g., (e.g., the former position of 756, asdepicted by the position of 776 on clock face 772).

In some embodiments, after receiving the first data representing thefirst user input, the device animates the stopwatch hand to represent arotational motion about an origin and ceases the animation to displaythe stopwatch hand at a position at π/2 radians (e.g., the 12 o'clockposition) relative to the rotational motion about the origin. Forexample, the stopwatch hand may function as a seconds hand of the clockface before the first data is received. When the first data is received,the seconds hand may be animated to depict a rotation around the clockface (e.g., by rotating about the center point of the clock face) untilit resets at the 12 o'clock position. This signals to the user that theseconds hand has now become the stopwatch hand.

Attention is now directed to the context-specific user interface shownin FIG. 8. FIG. 8 shows exemplary context-specific user interfaces thatmay be operated on device 800. Device 800 may be device 100, 300, or 500in some embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

FIGS. 8-10 provide context-specific user interfaces that allow the userto view the passage of time while accessing a rich array ofgeographical, lunar, and astronomical information. For example, a usermay have acquaintances all over the world and wish to know what parts ofthe world are in daytime or nighttime at a current time. A user may havean interest in the moon phase and wish to know what the Moon will looklike tomorrow, next week, or next month. A user may have an interest inastronomy and wish to know how the planets are aligned at a particulartime of interest, which could be the current day.

In FIG. 8, device 800 displays user interface screen 802 that includesfirst affordance 804. First affordance 804 represents a simulation of aregion of the Earth, as illuminated by the Sun at the current time. Forexample, first affordance 804 shows that North, Central, and SouthAmerica are currently in daytime, and part of the Pacific Ocean iscurrently in nighttime, thus simulating a region of the Earth asilluminated by the Sun at the current time.

Screen 802 also displays second affordance 806, which indicates thecurrent time. Second affordance 806 indicates the current time (10:09)and optionally includes an indication of the day of the week (Wednesday)and the day of the month (25^(th)). Screen 802 further displays moonaffordance 808 and solar system affordance 810, which are used to invokeadditional context-specific user interfaces accessible from this screenthat will be described in more detail below.

In some embodiments, the simulation of the first region of the Earth asilluminated by the Sun at the current time is a realistic rendering ofthe Earth at the current time. For example, the simulation of the Earthmay include specific geographic features. In some embodiments, thesimulation of the Earth is updated to reflect weather patterns at thecurrent time (e.g., by depicting cloud cover or other weather phenomenasuch as a tropical storm). The device may update the Earth to reflectglobal-scale by obtaining data from a weather service or externalserver, such as The Weather Channel, Accuweather, The National WeatherService, Yahoo!™ Weather, Weather Underground, the United States NavalObservatory, or the National Oceanic and Atmospheric Administration. Insome embodiments, the simulation of the first region of the Earth asilluminated by the Sun at the current time may indicate other globalevents, such as the real-time position of the International SpaceStation, which may be obtained from a service or external server such asfrom NASA.

Device 800 receives a user input (in this example, swipe 812), and inresponse to receiving the user input, device 800 rotates the simulationof the Earth to display a second region of the Earth as illuminated bythe Sun at the current time. This is depicted on screen 820, whichdisplays first affordance 822 depicting a second region of the Earth asilluminated by the Sun at the current time, which is indicated by secondaffordance 824. This feature allows the user to access additionalinformation other than the current time from this context-specific userinterface. For example, a user is able to rotate the simulation of theEarth and display which regions are currently in daytime and whichregions are currently in nighttime. Tying this information to asimulation of the Earth allows the user to access complex geographicaland time-related data in a manner that is instantly intuitive andcomprehensible.

In some embodiments, the first affordance representing the simulation ofthe first region of the Earth as illuminated by the Sun at the currenttime includes a representation of a solar terminator (e.g., a day/nightline at the current time). As illustrated by affordances 804 and 822,the simulation of the Earth may include a depiction of a region of theEarth currently in daytime, a region of the Earth currently innighttime, and/or a solar terminator dividing the two regions.

In some embodiments, the user input includes a swipe on thetouch-sensitive display in a first swipe direction, as illustrated byswipe 812. This allows the user to swipe the display to rotate thesimulation of the Earth. In some embodiments, the direction of rotationof the Earth is the same as the swipe direction. In some embodiments,the direction of rotation of the Earth is the opposite as the swipedirection.

In some embodiments, the user may rotate the simulation of the Earth inmore than one direction using swipes in different directions. Forexample, a swipe in one direction may cause the representation of theEarth to rotate in one direction, and a swipe in an opposite orotherwise different direction may cause the representation of the Earthto rotate in an opposite direction. This allows the user to swipe indifferent directions to direct the rotation of the simulation of theEarth.

In some embodiments, as illustrated in FIG. 8, the device has arotatable input mechanism (e.g., 506). Device 800 receives user inputrepresenting a movement of the rotatable input mechanism (e.g., movement830), and in response, device 800 updates first affordance 822 torepresent a simulation of the first region of the Earth as illuminatedby the Sun at a non-current time. This is shown on screen 840 with firstaffordance 842 and second affordance 844. Comparing screens 820 and 840,the simulation of the Earth has been updated (cf. 822 and 842) fromindicating a region of the Earth at the current time (10:09, indicatedby 824) to indicating the same region of the Earth at a non-current time(12:09, indicated by 844). This feature provides the user access tofurther geographic and time-related information by allowing the user toview the Earth, as illuminated by the Sun, at various times throughoutthe day.

In some embodiments, the device has a location sensor (e.g., GPS sensor532 and/or GPS module 135), and before displaying the user interfacescreen, the device obtains a current location of the electronic devicefrom the location sensor and displays the first region of the Earthrepresented by the first affordance to indicate the current location ofthe electronic device. This allows the device to display the Earth insuch a way that the current location is part of the visible portion ofthe simulation of the Earth, for example as a default or user-selectablestate. In some embodiments, the first affordance includes a visualmarking of the current location on the representation of the Earth. Thisallows the user to easily identify the current location on thesimulation of the Earth.

In some embodiments, the device (e.g., device 800) visually marks thecurrent location of the device on the representation of the Earth (e.g.,by displaying a symbol at the appropriate location on the representationof the Earth and/or text indicating the current location). In someembodiments, this visual marking may be transitory, e.g., the visualmarking may be displayed briefly and then disappear or fade out. In someembodiments, while the user is at the current location, the device doesnot repeat the visual marking of the current location. However, if theuser changes locations, the first time the user looks at the displayafter changing location, the device will visually mark the new currentlocation on the representation of the Earth as set forth above. In someembodiments, the device detects a user movement of the device (e.g., amovement of the device such as raising of the user's wrist, if thedevice is wearable, or other movement indicative that the user isviewing the display) and in response obtains a current location of theelectronic device from the location sensor. The device may thendetermine whether the current location is the same as the location ofthe device at the last user movement of the device. In accordance with adetermination that the current location has changed since the last usermovement of the device, the device may visually mark the currentlocation on the representation of the Earth.

In some embodiments, the device visually marks a location (e.g., acurrent location) corresponding to the location of a contact (e.g., thelocation of the contact's electronic device) on the representation ofthe Earth (e.g., by displaying a symbol at the appropriate location onthe representation of the Earth and/or text indicating the contact'slocation). The contact may be stored, e.g., on the device or on anexternal device that is coupled to the device via wireless communication(e.g., Wi-Fi, Bluetooth™, near field communication (“NFC”), or any ofthe other cellular and/or other wireless communication techniquesdescribed herein). In some embodiments, the contact may be a contactassociated with a user that has agreed to provide their location data tothe user of device 800, such as through a Find My Friends application,and data indicating the location of the contact's electronic device maybe provided through a server, which may provide the location of thecontacts stored on device 800. This provides the user of device 800 aquick visual reference to alert them to the current location of acontact. In some embodiments, the user may further input the travelinformation for a contact (e.g., flight data for a contact traveling byair, train data, cruise or boat data, etc.). The device may obtain datarepresenting the current or predicted location of the contact (provided,e.g., by an airline's server in the example of flight data) and updatethe visual marking of the contact's location based on the obtained data.

In some embodiments, the device detects a user movement of the device(e.g., a movement of the device such as raising of the user's wrist, ifthe device is wearable, or other movement indicative that the user isviewing the display). In response to detecting the movement, the deviceanimates the first affordance representing the simulation of the Earthby translating the first affordance on-screen towards the center of thedisplayed user interface screen. For example, upon detecting a usermovement, the device animates the simulation of the Earth to rotate infrom a side or edge of the display to the center of the display.

In some embodiments, the device displays on the user interface screen athird affordance representing a moon (as depicted by affordances 808,826, and 846). In some embodiments, the third affordance may be agraphical or stylized representation of a moon such as an icon, symbol,or a text indicating a moon. In some embodiments, the third affordancemay be a realistic rendering of the Moon as seen from the Earth at thecurrent time with actual lunar features depicted.

The device detects a contact on the displayed third affordance, and inresponse to detecting the contact, the device updates the display of theuser interface screen by displaying a fourth affordance representing asimulation of the Moon as seen from the Earth at the current time and afifth affordance indicating the current time. In some embodiments,updating the display of the user interface screen includes animating thefirst affordance representing the simulation of the first region of theEarth as illuminated by the Sun by zooming out. This animation allowsthe user to recognize that the astronomical scale and/or perspective haschanged.

This transitions the user interface from providing information about thecurrent time within the current day using a simulation of the Earth toproviding information about the current time within the current monthusing a simulation of the Moon. Whereas the context-specific userinterface described in reference to FIG. 8 provides the user worldwide,customizable geographical information about day/night conditions, acontext-specific user interface that provides the user customizableinformation about moon phases and other lunar features is illustrated inFIG. 9.

FIG. 9 shows exemplary context-specific user interfaces that may beoperated on device 900. Device 900 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

As described above, device 900 is device 800 with an updated display.Device 900 is displaying screen 902, which includes affordance 904.Affordance 904 represents a simulation of the Moon as seen from theEarth at the current time (e.g., the current moon phase). In someembodiments, fourth affordance 904 is a realistic rendering of the Moonas seen from the Earth at the current time with actual lunar featuresdepicted. As shown by fourth affordance 904, the current moon phase is awaning crescent moon. Although FIG. 9 shows a stylized crescent moon forthe representation of the Moon, this is a schematic for illustrativepurposes only. Fourth affordance 904 may depict a realistic rendering ofthe Moon, similar to how the Moon actually appears in the night sky.Screen 904 also includes fifth affordance 906, which illustrates thecurrent time by showing the current date, day of the week, and month. Insome embodiments, 906 indicates the current time of the day.

Device 900 receives a user input (e.g., movement 912 of the rotatableinput mechanism), and in response to receiving the user input, thedevice rotates the simulation of the Moon to display the Moon as seenfrom the Earth at a non-current time, as shown on screen 920 byaffordance 922, which represents the Moon at a non-current time, whichis indicated by updated fifth affordance 924. A non-current time may bewithin the current month or in a different month.

This is somewhat analogous to the user interaction with the simulationof the Earth described for FIG. 8. The context-specific user interfaceexemplified in FIG. 9 allows the user to access information about theappearance of the Moon (e.g., Moon phase, or which regions of the Moonmay be visible from Earth) at various times. In some embodiments, thesize of the displayed simulation of the Moon may be representative ofthe relative distance between the Earth and the Moon at the depictedcurrent or non-current time, or it may be representative of the visualsize of the Moon at the depicted current or non-current time asperceived from Earth. The device may obtain such information from, e.g.,a service or external server such as from NASA.

In some embodiments, a user may rotate the representation of the Moonand view corresponding times by swiping the touch-sensitive display. Insome embodiments, the user input may include a swipe on thetouch-sensitive display in a first swipe direction. In some embodiments,in response to receiving the user input, the simulation of the Moon asseen from the Earth is rotated in a first direction of rotation. In someembodiments, the first direction of rotation may be based at least inpart on the first swipe direction. As used herein, a rotation of theMoon may include a rotation of the Moon on its axis to depict adifferent region of the Moon (e.g., a region of the Moon not visiblefrom the Earth) and/or updating the appearance of the Moon as viewedfrom Earth at a particular time of interest, based on a rotation of therelative positions of the Moon, Earth, and Sun (e.g., updating thedisplayed lunar phase).

In some embodiments, the device receives a second user input, and inresponse to receiving the second user input, the device rotates thesimulation of the Moon as seen from the Earth in a second direction ofrotation that is different from the first direction. This user inputcould include, e.g., a swipe on the touch-sensitive display in a secondswipe direction that is different from the first swipe direction.

This allows the user to direct both the direction of rotation of theMoon, and the time indicated by the fifth affordance, in response toswiping. For example, the user may swipe in one direction to rotate theMoon in a specific direction and view the Moon at later times in themonth, and the user may swipe in another direction to rotate the Moon inan opposite direction and view the Moon at earlier times in the month.

In some embodiments, as shown in FIG. 9, a user may rotate therepresentation of the Moon and view corresponding times by rotating arotatable input mechanism. Thus, in some embodiments, the device has arotatable input mechanism (e.g., 506), and the user input may include amovement of the rotatable input mechanism in a first direction ofrotation (e.g., rotation 912). In some embodiments, in response toreceiving the user input, the simulation of the Moon as seen from theEarth is rotated in a first direction of rotation. In some embodiments,the first direction of rotation may be based at least in part on thedirection of movement of the rotatable input mechanism.

In some embodiments, the device receives a second user input, and inresponse to receiving the second user input, the device rotates thesimulation of the Moon as seen from the Earth in a second direction ofrotation that is different from the first direction. This user inputcould include, e.g., a movement of the rotatable input mechanism in asecond direction of rotation that is different from the first directionof rotation.

This allows the user to direct both the direction of rotation of theMoon, and the time indicated by the fifth affordance, in response torotating the rotatable input mechanism. For example, the user may movethe rotatable input mechanism in one direction to rotate the Moon in aspecific direction and view the Moon at later times in the month, andthe user may move the rotatable input mechanism in another direction torotate the Moon in an opposite direction and view the Moon at earliertimes in the month.

In any of the embodiments described herein, the displayed simulation ofthe Moon may indicate one or more additional lunar attributes, such asspecial moons (e.g., blue, black, or red moons, lunar eclipses, and soforth), the distance between the Moon and the Earth (as described above,e.g., for a supermoon), and/or moon wobble. In some embodiments, theadditional lunar attribute(s) may be indicated by altering theappearance of the displayed simulation of the Moon (e.g., by changingthe color, size, and/or tilt of the displayed simulation of the Moon).In some embodiments, the additional lunar attribute(s) may be indicatedby text. In some embodiments, the additional lunar attribute(s) maycorrespond to the current lunar attribute(s). In some embodiments, theadditional lunar attribute(s) may correspond to the lunar attribute(s)at the currently displayed date (e.g., if the user has rotated the Moonto view the Moon at earlier or later times in the month, as describedabove). For example, in some embodiments, while the simulation of theMoon is being rotated to depict the Moon at different times of the monthor year, the simulation of the Moon may be updated to reflect one ormore additional lunar attributes at the time currently indicated by thedisplayed simulation of the Moon.

In some embodiments, the device may display additional lunar informationin response to a user input. The additional lunar information may bedisplayed, e.g., as part of screen 902 or 920, or on a user interfacescreen that replaces screen 902 or 920 (such as a lunar informationapplication). Additional lunar information may include withoutlimitation the name of the lunar phase, the distance from the Earth tothe Moon, the time of moonrise and/or moonset (e.g., on the current dayand/or at the user's current location), and the like. In someembodiments, the additional lunar information may correspond to thecurrent lunar information (e.g., the current lunar phase, distance tothe Moon, time of moonset/moonrise, etc.). In some embodiments, theadditional lunar information may correspond to the lunar information ofthe currently displayed date, e.g., if the user has rotated the Moon toview the Moon at earlier or later times in the month, as describedabove.

For example, in some embodiments, the device may detect a user input(e.g., a user double tap on the touch-sensitive display, including afirst contact on the touch-sensitive display and a second contact on thetouch-sensitive display). In the exemplary embodiment and in response tothe user double tap, the device may determine whether the first contactand the second contact were received within a predetermined interval. Inresponse to detecting the user double tap, and in accordance with thedetermination that the first contact and the second contact werereceived within the predetermined interval, the device may displayadditional lunar information.

In some embodiments, the user interface screen, after updating thedisplay to show the simulation of the Moon, displays an affordanceindicating an earth (e.g., 910 or 928). Upon contacting the earthaffordance, the user may return to the context-specific user interfacedescribed in reference to FIG. 8. In some embodiments, the earthaffordance may be a graphical or stylized representation of an earthsuch as an icon, symbol, or a text indicating an earth. In someembodiments, the earth affordance may be a realistic rendering of theEarth.

In some embodiments, device 900 displays on the user interface screen asixth affordance representing a solar system (as depicted by affordances810, 828, 848, 908, and 926). In some embodiments, the sixth affordancemay be a graphical or stylized representation of a solar system such asan icon, symbol, or a text indicating a solar system. In someembodiments, the sixth affordance may be a realistic rendering of thesolar system.

Device 900 detects a contact on the displayed sixth affordance, and inresponse to detecting the contact, the device updates the display of theuser interface screen by displaying a seventh affordance withrepresentations of the Sun, the Earth, and one or more non-Earth planetsat their respective positions at the current time and an eighthaffordance indicating the current time. In some embodiments, updatingthe display of the user interface screen includes animating the firstaffordance representing the simulation of the first region of the Earthas illuminated by the Sun or animating the fourth affordancerepresenting a simulation of the Moon as seen from the Earth by zoomingout. This animation allows the user to recognize that the astronomicalscale and/or perspective has changed.

This transitions the user from viewing information about the currenttime within the current month using a simulation of the Moon to viewinginformation about the current time within the current year using asimulation of the solar system. Whereas the context-specific userinterface described in reference to FIG. 9 provides the usercustomizable information about lunar conditions, a context-specific userinterface that provides the user customizable information about thesolar system and relative positions of the Earth and other planet(s) isillustrated in FIG. 10.

FIG. 10 shows exemplary context-specific user interfaces that may beoperated on device 1000. Device 1000 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

As described above, device 1000 is device 800 and/or device 900 with anupdated display. Device 1000 displays screen 1002, which includesseventh affordance 1004. Seventh affordance 1004 includes representationof the Sun 1006, representation of the Earth 1008, and representationsof Mercury, Venus, and Saturn (e.g., Saturn is depicted by planet 1010).1006, 1008, and 1010 are depicted at their respective positions at thecurrent date (in this example, May 25, 2014), indicated by eighthaffordance 1012. In some embodiments, eighth affordance 1012 alsoindicates the current time of day.

Optionally, in some embodiments, the solar system depicts all 8 planets.In some embodiments, the solar system depicts the four inner planets. Insome embodiments, the solar system depicts other astronomical features,such as an asteroid or asteroid belt, one or more moons of one or moreplanets (e.g., the Moon), a manmade satellite or other space probe, acomet, Pluto, and so forth.

Device 1000 receives a seventh user input (e.g., movement 1018 of therotatable input mechanism). In response, device 1000 updates the seventhaffordance to depict respective positions of the Sun, the Earth, and theone or more non-Earth planets for a non-current date. This is depictedby seventh affordance 1022 on screen 1020. Seventh affordance 1022includes representation of the Sun 1024, representation of the Earth1026, and representations of Mercury, Venus, and Saturn (e.g., Saturn isdepicted by planet 1028) at their respective positions at thenon-current date, which is Nov. 25, 2014, as depicted by eighthaffordance 1030. In some embodiments, eighth affordance 1030 alsoindicates the current time of day.

This context-specific user interface allows the user to accessinformation about the relative positions of the Earth and one or morenon-Earth planets at a non-current date, which may be within the currentyear or in a different year. In some embodiments, the Sun, the Earth,and the one or more non-Earth planets are depicted as realisticrenderings. In some embodiments, the Sun, the Earth, and the one or morenon-Earth planets are depicted as stylized or symbolic renderings.

In some embodiments, a user may rotate the representation of the solarsystem by swiping on the touch-sensitive display. Thus, in someembodiments, the user input may include a swipe on the touch-sensitivedisplay. In some embodiments, in response to detecting a swipe, theEarth and the one or more non-Earth planets are rotated about the Sun ina first direction of rotation. In some embodiments, the first directionof rotation may be based at least in part on the first swipe direction.

In some embodiments, in response to detecting a swipe on thetouch-sensitive display in a different direction, the device rotates theEarth and the one or more non-Earth planets about the Sun in a seconddirection of rotation that is different from the first direction. Thisallows the user to direct both the direction of rotation of the Earthand the one or more non-Earth planets, and the time indicated by theeighth affordance, in response to swiping. For example, the user mayswipe in one direction to rotate the Earth and the one or more non-Earthplanets in a specific direction and view the Earth and the one or morenon-Earth planets at later dates during the year (or in a differentyear), and the user may swipe in another direction to rotate the Earthand the one or more non-Earth planets in an opposite direction and viewthe Earth and the one or more non-Earth planets at earlier dates duringthe year (or in a different year).

In some embodiments, as shown in FIG. 10, a user may rotate therepresentation of the solar system by rotating a rotatable inputmechanism (e.g., 506). In these embodiments, the user input may includea movement of the rotatable input mechanism in a first direction ofrotation (e.g., movement 1018). In some embodiments, in response toreceiving the user input, the Earth and the one or more non-Earthplanets are rotated about the Sun in a first direction of rotation. Insome embodiments, the first direction of rotation may be based at leastin part on the direction of movement of the rotatable input mechanism.

In some embodiments, the device receives a second user input, and inresponse to receiving the second user input, the device rotates theEarth and the one or more non-Earth planets about the Sun in a seconddirection of rotation that is different from the first direction. Thisuser input could include, e.g., a movement of the rotatable inputmechanism in a second direction of rotation that is different from thefirst direction of rotation.

This allows the user to direct both the direction of rotation of theEarth and the one or more non-Earth planets, and the time indicated bythe eighth affordance, in response to rotating the rotatable inputmechanism. For example, the user may move the rotatable input mechanismin one direction to rotate the Earth and the one or more non-Earthplanets in a specific direction and view the Earth and the one or morenon-Earth planets at later times in the year, and the user may move therotatable input mechanism in another direction to rotate the Earth andthe one or more non-Earth planets in an opposite direction and view theEarth and the one or more non-Earth planets at earlier times in theyear.

In some embodiments, the representation of the Earth may further includea representation of the orbit of the Earth around the Sun. In someembodiments, the representation of the one or more non-Earth planets mayfurther include a representation of the orbit of the one or morenon-Earth planets around the Sun. The representation of an orbit may bea graphical representation, such as a line or ring. In some embodiments,the representation of the orbit may be stylized. In some embodiments,the representation of the orbit may be based on the actual dimensions ofthe planet's orbit around the Sun.

In some embodiments, the user may contact the touch-sensitive display ata location associated with the representation of the Earth or the one ormore non-Earth planets. For example, the contact may be at or near thedisplayed representation of the planet itself, or the contact may be ator near the displayed representation of the planet's orbit. In someembodiments, the device may determine the selected planet based on adetermination of the displayed representation of a planet or thedisplayed representation of a planet's orbit nearest to the location ofthe contact. In some embodiments, the contact may be a press andhold-type contact on the display. Upon detecting the contact, the devicemay visually distinguish the representation of the selected planetand/or the representation of the selected planet's orbit (e.g., byaltering the color and/or brightness of the displayed planet and/ororbit, by displaying an outline or other visual demarcation of theplanet and/or orbit, by animation the planet and/or orbit, etc.). Insome embodiments, while continuing to receive the contact, the devicemay determine whether the duration of the contact exceeds apredetermined threshold and, in accordance with a determination that thecontact exceeds the predetermined threshold, the device may visuallydistinguish the representation of the selected planet and/or therepresentation of the selected planet's orbit. When the user lets go ofthe contact, the device may display information about the selectedplanet. Such information may include, without limitation, the size ofthe planet, the distance (e.g., current distance, average distance,etc.) between the planet and the Sun, the distance (e.g., currentdistance, average distance, etc.) between the planet and the Earth (ifthe selected planet is not the Earth), a time and/or location in the skywhen the planet will be visible from the Earth (if the selected planetis not the Earth), a temperature on the surface of the planet, thenumber of moons orbiting the planet, the number and/or identity of anyspacecraft currently orbiting or near the planet, a description of theplanet (e.g., whether the planet is terrestrial or gas, the date ofdiscovery of the planet, information about the planet's name, and thelike), a time (past, present, or future) of a particular alignment ofthe planet with another object in the solar system, and so forth.

After viewing the information about the planet, the user may wish todismiss the information or view information about another planet. Insome embodiments, the user may tap to dismiss the information or swipeto select another planet. For example, a swipe in a first direction mayselect the next planet whose orbit is farther from the Sun, relative tothe previous planet, and a swipe in the opposite direction may selectthe next planet whose orbit is nearer to the sun, relative to theprevious planet. In some embodiments, after displaying the informationabout the Earth or the one or more non-Earth planets associated with thecontact, the device may receive a user input and determine whether theuser input represents a tap or a swipe on the touch-sensitive display(e.g., by using contact/motion module 130 to detect the user gesture).In accordance with a determination that the user input represents a tap,the device may remove the displayed information about the planet. Inaccordance with a determination that the user input represents a swipe,the device may replace the displayed information about the planet withinformation about a second planet different from the first planet (e.g.,a planet not associated with the user contact).

In some embodiments, the user interface screen, after updating thedisplay to show the simulation of the solar system, displays anaffordance indicating a moon (e.g., 1016 or 1034) and/or an affordanceindicating an earth (e.g., 1014 or 1032). In some embodiments, the moonand/or the earth affordance may be a graphical or stylizedrepresentation of an earth or moon such as an icon, symbol, or a text.In some embodiments, the moon and/or the earth affordance may be arealistic rendering of the Moon or the Earth. Upon contacting the earthaffordance, the user may return to the context-specific user interfacedescribed in reference to FIG. 8. Upon contacting the moon affordance,the user may return to the context-specific user interface described inreference to FIG. 9.

In some embodiments of any of the context specific-user interfacesillustrated in FIGS. 8-10, a user may move (e.g., rotate) a rotatableinput mechanism to scroll a displayed indication of time forward orbackward in time. It is to be appreciated that such a feature may beapplied to any of the context-specific user interfaces described herein;however, for ease of explanation, this feature may be described inreference to FIGS. 8-10. Any model for mapping a movement of a rotatableinput mechanism to the distance or speed of scrolling may be used, suchas those described in U.S. patent application Ser. No. 14/476,700,“Crown Input for a Wearable Electronic Device,” filed Sep. 3, 2014,which is hereby incorporated by reference in its entirety. For example,acceleration, velocity, or the like may be used to determine the amountof speed of scaling of the displayed indication of time.

In some embodiments, a user may move the rotatable input mechanism toscroll the indication(s) of time displayed on screen 802, 820, and/or840. In response to detecting the movement of the rotatable inputmechanism (e.g., movement 830), the device may update the displayedrepresentation of the Earth, for example by simulating a rotation of theEarth, to display the Earth as illuminated by the Sun at a differenttime of day (compare 822 and 842). In some embodiments, the device mayupdate the displayed indication of time to show a different time(compare 824 and 844). Similarly, as shown in FIG. 9, in response todetecting the movement of the rotatable input mechanism (e.g., movement912), the device may update the displayed simulation of the Moon todisplay a different moon phase at a different time of month (compare,e.g., 904 and 922), and/or update the displayed indication of time toshow a different time (compare, e.g., 906 and 924). Similarly, as shownin FIG. 10, in response to detecting the movement of the rotatable inputmechanism (e.g., movement 1018), the device may update the displayedpositions of the Earth and the one or more non-Earth planets to displaydifferent positions relative to the Sun at different times of year(compare, e.g., 1008 and 1010 to 1026 and 1028), and/or update thedisplayed indication of time to show a different time (compare, e.g.,1012 and 1030). In some embodiments, the representations of the Earth,the Moon, and/or the positions of the Earth and the one or morenon-Earth planets may be rotated in a direction based on the directionof movement of the rotatable input mechanism. In some embodiments, therepresentations of the Earth, the Moon, and/or the positions of theEarth and the one or more non-Earth planets may be rotated at a ratebased on the rate and/or amount of movement of the rotatable inputmechanism, e.g., according to any of the models referenced above. It isto be appreciated that, depending on the displayed context-specific userinterface, movement of the rotatable input mechanism may cause thedisplayed indication of time to be updated at different timescales. Forexample, the same degree and/or rate of rotation may cause thecontext-specific user interface shown in FIG. 8 to update by an hour,whereas the context-specific user interface shown in FIG. 9 may updateby a day or week, or the context-specific user interface shown in FIG.10 may update by a month or year.

In some embodiments of any of the context specific-user interfacesillustrated in FIGS. 8-10, the device may indicate other global orastronomical features or objects, such as the real-time position of theInternational Space Station, as described above. In some embodiments, auser may tap on the display (e.g., at a location corresponding tospace), and in response to detecting the tap, the device may providefurther information on other global or astronomical features or objects,e.g., the number of people currently in space, the number and/or name(s)of spacecraft currently in space, etc.

FIG. 11A shows exemplary context-specific user interfaces that may beoperated on device 1100. Device 1100 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

A user may wish to view the time of day in the context of daytime andnighttime hours. For example, a user may wish to know the time of dawnor dusk, or access a simple, visual indication of how much time is leftbefore sunset.

As shown in FIG. 11A, device 1100 displays user interface screen 1102.User interface screen 1102 has two portions: first portion 1104indicating daytime, and second portion 1106 indicating nighttime. Screen1102 also displays a user interface object representing a sinusoidalwave 1108. Sinusoidal wave 1108 may represent the general appearance ofa sinusoidal wave without mathematical accuracy or precision.Importantly, however, sinusoidal wave 1108 has a period of approximatelya day and indicates the path of the Sun through the day. As shown inFIG. 11A, the troughs of 1108 represent solar midnight (corresponding totwo solar midnights 24 hours apart), and the peak of 1108 representssolar noon for the day. Also displayed on screen 1102 is firstaffordance 1110, which is displayed at a position along sinusoidal wave1108 at a position that indicates the current time of day. Screen 1102also displays horizon line 1112, an optional feature which divides thedaytime and nighttime portions of the display. As shown, horizon line1112 intersects sinusoidal wave 1108 at two points, representing sunriseand sunset. Finally, screen 1102 displays second affordance 1114, whichindicates the current time of day.

Through the course of the day, 1114 displays the current time (in thisexample, 5:30 am), and first affordance 1110 tracks along the sinusoidalwave. When 1110 is in daytime portion 1104, the current time is duringdaytime. When 1110 is in nighttime portion 1106, the current time is innighttime. At 5:30 am, it is just before dawn, as first affordance 1110is still in the nighttime portion of screen 1102. The features of thiscontext-specific user interface provide the user a simple and intuitiveway to track the current time and understand how long it is until, forexample, sunset, or sunrise. In some embodiments, the affordancerepresenting the sun appears hollow (e.g., like a ring) when at aposition fully within the nighttime portion (e.g., 1106) of the display,as shown by first affordance 1110. This further reinforces to the userthat it is currently before dawn.

For example, screen 1120 shows a second time of day and includes firstaffordance 1122, sinusoidal wave 1124, and second affordance 1126. Asindicated by second affordance 1126, it is now sunrise at 7:00 am. Theposition of first affordance 1122 along wave 1124 is between the firstportion and the second portion, indicating the transition from nighttimeto daytime. This is further depicted on screen 1120 by positioningaffordance 1122 on line 1128, which separates the two portions of thedisplay. This is yet further indicated by the appearance of affordance1122 itself, which, optionally, may be half-filled when the affordanceis at a position intersecting the first and second portions of thedisplay.

Screen 1130 shows a third time of day and includes first affordance1132, sinusoidal wave 1134, and second affordance 1136. As indicated bysecond affordance 1136, it is now 2:00 pm. The position of firstaffordance 1132 along wave 1134 is within the first portion of thedisplay, indicating daytime. This is further depicted by the appearanceof affordance 1132 itself, which, optionally, may be filled when theaffordance is at a position fully within the first portion.

In some embodiments, the color of the first and/or the second portion(s)may indicate daytime (e.g., with a warm or bright color) or nighttime(e.g., with a dark or cool color). In some embodiments, the first andsecond portions may be the same color, which may be representative ofthe current light conditions. In these embodiments, the user may stillbe able to tell the current light conditions through the sinusoidalwave, optional horizon line, and/or optional appearance of the sunaffordance (e.g., filled, half-filled, or hollow). In some embodiments,the sinusoidal wave may include two or more colors, and these colors mayindicate the daytime and nighttime portions (e.g., parts of the wave inthe daytime portion may be one color, and parts of the wave in thenighttime portion may be another). Moreover, the two portions may be ofany shape (not limited to rectangular). For example, the daytime portionmay appear as an illuminated circle that encompasses the sinusoidalwave, with the nighttime portion appearing all around the circle.

In some embodiments, device 1100 may have a location sensor (e.g., GPSsensor 532 and/or GPS module 135). In these embodiments, device 1100 mayobtain a current location of the device from the location sensor andindicate daytime and nighttime hours at the current location at thecurrent time through the ratio of the displayed first and secondportions. That is to say, the size of the daytime and nighttime portionsof the display may be adjusted, relative to daytime hours at the currentlocation and date. As an illustrative example, if the current locationis near the Arctic Circle during summer, the daytime portion may includeall or nearly all of the screen, such that all or nearly all of thedisplayed sinusoidal wave is within the daytime portion. As anotherexample, if the user were to travel latitudinally across the globe, theposition of affordance 1110, 1122, or 1132 (for example) would notchange, but the ratio of daytime:nighttime portions and relative amountof the sinusoidal wave within each would be adjusted to reflect thecurrent location. This provides a more realistic depiction of the timeof day to the user, thus enhancing the user interface.

In some embodiments, the amplitude of the displayed sinusoidal wave isbased on the height of the Sun relative to the horizon at the currentlocation and current time. For example, the wave may flatten orotherwise decrease in amplitude to reflect the sun having a lower paththrough the sky at the location and current day (e.g., in locations moreproximal to the poles in winter).

Attention is now directed to FIG. 11B, which illustrates an example ofthis context-specific user interface that provides a user-interactablefeature to view additional day/night information. FIG. 11B shows userinterface screen 1140 that can be displayed on device 1100. Screen 1140includes first affordance 1142, which represents the position of the sunat the current time along sinusoidal wave 1144. Screen 1140 alsodisplays second affordance 1146, which also indicates the current time(10:09 am). Device 1100 receives a user contact at displayed firstaffordance 1142, shown by touch 1148.

As detected by device 1100, the user touches first affordance 1142 anddrags the affordance to a second position along the sinusoidal wave in acontinuous gesture (as indicated by touch 1166). In response, as shownon screen 1160, device 1100 displays first affordance 1162 at the secondposition along sinusoidal wave 1164. Device 1100 also updates the secondaffordance 1168 to indicate a non-current time. This new time (12:09)corresponds to the time of day indicated by the second position ofaffordance 1162. Thus, the user is able to view the time of dayrepresented by any position along the sinusoidal wave by simply movingaffordance 1148 and/or 1166.

It is to be noted that the movement of the contact may begin and end atpositions on the sinusoidal wave, but the movement itself need notprecisely track the sinusoidal wave. That is, the user is not requiredto track the contact precisely along the sinusoidal wave. The device maysimply receive a user contact at the displayed first affordance, and,while continuing to receive the user contact, detect a movement of thecontact from the first position to a second position without a break inthe user contact on the touch-sensitive display (e.g., the user does notlift their finger off the touch-sensitive display).

In response to detecting the contact at the second position, the devicemay translate the first affordance on-screen to the second positionwhile tracking the sinusoidal wave. Thus, while the user contact doesnot need to track the sinusoidal wave, the device nonetheless translatesthe first affordance from the first position to the second position bytracking the first affordance along the sinusoidal wave. In someembodiments, the device may continuously update the time, as indicatedby the second affordance. Alternatively, the device may update the timeindicated by the second affordance when the continuous contact has cometo rest at the second position. In alternative embodiment, afterdetecting the contact at the first position, the device may translatethe first affordance on-screen to the second position on the sinusoidalwave in response to a rotation of a rotatable input mechanism.

FIG. 11B illustrates optional features of this context-specific userinterface. As shown on screen 1140, in response to receiving user touch1148 at affordance 1142, device 1100 displays affordances 1150 and 1152,which depict sunrise and sunset, respectively. Affordances 1150 and 1152are displayed along wave 1144 at the two points where the waveintersects the boundary between the first portion indicating daytime andthe second portion indicating nighttime. This boundary is demarcated onscreen 1140 with optional horizon line 1154. When horizon line 1154 isdisplayed, affordances 1150 and 1152 are displayed at the two pointswhere line 1154 intersects wave 1144. In some embodiments, affordances1150 and 1152 may further include a numerical display of sunrise andsunset times, respectively, for the current day. In some embodiments,these affordances are also displayed while device 1100 receives usercontact at the second position.

Also displayed on screen 1140 in response to receiving user touch 1148at affordance 1142 are affordances 1156 and 1158. Affordances 1156 and1158 are displayed along wave 1144 at positions corresponding to dawnand dusk, respectively. In some embodiments, these affordances are alsodisplayed while device 1100 receives user contact at the secondposition. These displayed affordances indicate to the user when firstand last light will occur, allowing the user to visually gauge when theywill occur, or how long ago they occurred, by the distance fromaffordance 1142. In some embodiments, the time of dawn may beastronomical dawn, nautical dawn, or civil dawn. In some embodiments,the time of dusk may be astronomical dusk, nautical dusk, or civil dusk.

In some embodiments, device 1100 detects a contact at the displayedfirst affordance, a movement of the contact, and a break in contact. Inresponse to detecting the break in contact, the device may translate thefirst affordance back to the position indicating the current time andupdate the second affordance to indicate the current time. This allowsthe user to drag the affordance to a position of interest, view theindicated time for that position, and by releasing the contact, “snapback” to the current position.

FIG. 11C illustrates further optional features of this context-specificuser interface. In some embodiments, particularly when the userinterface screen is displayed on a reduced-size display, it may bedesirable to display each of the elements as large as possible forvisibility. Screen 1170 displays first affordance 1172, sinusoidal wave1174, and second affordance 1176. As shown, affordance 1176 intersectswave 1174. When the current time reaches 2:00, as shown on screen 1180,the position of affordance 1182 indicating 2:00 along wave 1184intersects with the position of the second affordance. Device 1100 maydetermine whether the position of the first affordance intersects withthe second affordance (e.g., a position that would overlap with, beobscured by, or otherwise appear close to the second affordance). Inresponse to a determination that the affordances intersect, the devicemay display the second affordance at another position on the displaythat does not intersect. As illustrated on screen 1180, the position ofaffordance 1186 is different from that of 1176, because the relativeposition of 1176 on the screen would intersect with first affordance1182. This accommodation allows the device to display a richlyinformative screen without visual interference between displayedelements.

The user may also contact the touch-sensitive display with touch 1188 onscreen 1180. This contact may be, for example, at any position on thedisplay besides the position of the first affordance representing thesun at the current time. In response to detecting the contact, device1100 displays screen 1190, which includes sunrise time 1192, sunset time1194, and affordance 1196, which provides a non-textual indication ofdaytime and nighttime. This allows the user to access sunrise and sunsettimes from any user interface screen.

The user may also set a reminder for a time of day through thiscontext-specific user interface. For example, if the device has arotatable input mechanism (e.g., 506), the user may rotate the rotatableinput mechanism to set the reminder. In response to detecting a movementof the rotatable input mechanism, the device may translate the firstaffordance to a third position indicating a non-current time of day. Theuser may contact the first affordance displayed at the third position,and in response to detecting the contact, the device may set a userreminder for the indicated time of day.

For example, the device may display another affordance representing auser prompt to set an alert for the indicated time of day. The remindercould be a visual alert. In this example, the device may display avisual alert that is displayed when the time of day is approaching.Alternatively, the device may display at any time a visual affordancethat shows the third position along the sinusoidal wave to help the userunderstand how far the indicated time of day is from the current time.In some embodiments, the user reminder could include an audio alert thataudibly notifies the user when the indicated time of day has arrived orwill arrive shortly. In some embodiments, the user reminder couldinclude a haptic alert. The device may create a haptic signal to theuser when the indicated time of day is approaching (e.g., using hapticfeedback module 133 and tactile output generator 167).

These features allow the user to further customize this context-specificuser interface. It is to be appreciated that this feature does notcreate a specific alert at a time and date; rather, it allows the userto set a generic alert for a time of day that is not tied to a specificdate. For example, a user may notice a certain lighting effect, such assunlight through a window in their house, and wish to set a reminder sothat they can view this effect at the time of day when it occurs. Withinthe context of daytime/nighttime information, this allows the user tocustomize the user interface to include not only sunrise, sunset, dawn,dusk, and so forth, but also a time of day that they wish to designate.

FIG. 12 shows exemplary context-specific user interfaces that may beoperated on device 1200. Device 1200 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

A user may wish to view a certain background image on the user interfacescreen while retaining as much of the original image as possible.Therefore, it may be advantageous to provide a context-specific userinterface that displays the time and/or date not simply as interfaceobjects displayed over the image, but rather interface objects thatappear to arise from the image itself, thereby maximizing the user'sview of the image while still providing visible indications of the timeand date. This may be particularly true if the user interface isdisplayed on a reduced-size display.

As shown in FIG. 12, device 1200 is displaying user interface screen1202, which includes background 1204. Background 1204 is based on animage of a beach. In some embodiments, the image may be a photo.

As used here, consistent with its accepted meaning in the art, thephrase “background” refers to the background of a user interface screenthat is visually distinguishable from text and user interface objectsalso displayed in the user interface screen. Basing a background on animage simply means displaying the image as a background of a displayedscreen. In some cases, the image and the background may be identical. Inother cases, displaying the image as a background may involve modifyingone or more aspects of the image to fit on the display, such as imagesize, image cropping, image resolution, and so forth.

Screen 1202 also includes user interface objects 1206 and 1208. 1206indicates a date (the 23^(rd)), whereas 1208 indicates a time of day(10:09). In some embodiments, the device may indicate the current dateand/or the current time of day.

Displayed background 1204 includes a plurality of pixels. A subset ofthese pixels is modified in appearance relative to the image such thatthe subset comes to represent one or more of user interface object 1206and user interface object 1208. That is to say, at least one of theseuser interface objects is displayed by modifying the background. Forexample, the subset of pixels may be modified by changing color and/orintensity.

In some embodiments, the subset of the pixels may be modified by colorblending. In some embodiments, the subset of the pixels may be modifiedby color blurring. In some embodiments, the subset of the pixels may bemodified by applying a gradient. Importantly, these examples illustratethat the appearance of the subset of the pixels may be influenced byboth the background image at the position of the user interfaceobject(s) and the user interface object(s) themselves. This allows theuser to view the image more clearly (since the user interface object(s)are not simply displayed on top of and obstructing the image), whilealso maintaining the legibility of the user interface object(s).

In some embodiments, one of user interface objects 1206 and 1208 isdisplayed by modifying the background, and the other is displayedindependent of the background (e.g., a set color and/or intensity notproduced by modifying the background pixel subset). In theseembodiments, the device may receive data representing a background colorat the position of the displayed user interface object (e.g., 1206 or1208), and the color of the displayed user interface object may bedifferent from this background color (e.g., a different color and/orintensity). For example, a background color at the position of thedisplayed user interface object may include the most prevalent color atthat position. This feature ensures that, if one of the user interfaceobjects is a preset color, it will be displayed legibly on thebackground, no matter the appearance of the background.

In some embodiments, the image on which the background is based may bestored on device 1200.

In other embodiments, the image on which the background is based may bestored on an external device that is coupled to device 1200 via wirelesscommunication (e.g., Wi-Fi, Bluetooth™, near field communication(“NFC”), or any of the other cellular and/or other wirelesscommunication techniques described herein). In these embodiments, beforedisplaying screen 1202, device 1200 may receive (via wirelesscommunication) data representing the background from the externaldevice. Using these data, device 1200 may then display the background.

Optionally, when the image is stored on an external device, device 1200may display a background based on the current background of the externaldevice. For example, the device may receive (via wireless communication)data representing a current background from the external device anddisplay a user interface screen that includes a background correspondingwith the current background of the external devices. The device thenmodifies a subset of the pixels of the background from the externaldevice to represent one or more of a user interface object indicating adate and a user interface object indicating a time of day. In someembodiments, device 1200 may further alter the background from theexternal device, for example, by changing one or more of the image size,image cropping, image resolution, and the like, particularly if theexternal device and device 1200 have different display dimensions and/orresolutions.

Returning to FIG. 12, a user may wish to select an image from a folderof images to serve as the background. Thus, device 1200 may access afolder that includes two or more images (e.g., the images shown onscreens 1202 and 1210), select a first image, and display a userinterface screen that includes a background based on the first image(e.g., background 1204). As described above, this background includes asubset of pixels that are modified in appearance relative to the imageto represent one or more of a user interface object indicating a date(e.g., 1206) and a user interface object indicating a time (e.g., 1208).

Optionally, as shown in FIG. 12, after displaying screen 1202, device1200 may receive data representing a user input. In response, device1200 obtains data representing background 1204, select a second imagefrom the folder that is different from the first image, and displayscreen 1210, which includes background 1212 based on the second image.As shown in FIG. 12, backgrounds 1204 and 1212 are based on differentimages: a beach scene and a mountain scene, respectively. This featureensures that, when the user decides to change the displayed background,the device displays a different image, compared to the image displayedbefore the user input.

As shown on FIG. 12, screen 1210 also includes user interface object1214 indicating a date and user interface object 1216 indicating a timeof day. At least one of these user interface objects is displayed bymodifying a subset of pixels of background 1212 at the position of thedisplayed user interface object(s), as described above. This subset maybe modified in any of the ways described above, such as color blending,blurring, gradient, etc. In some embodiments, one of the user interfaceobjects may be a color independent of the background, and device 1200may modify this color to adapt to the background, as set forth above.The image on which the background is based may be stored on device 1200or on an external device, as described above.

A variety of user inputs may serve as the user input to change thebackground. In some embodiments, the user input may be a touch on thedisplay, a rotation of a rotatable input mechanism, a depression of adepressible and rotatable input mechanism, or a swipe on the display. Insome embodiments, the user input may be a user movement of theelectronic device (e.g., a movement of the device such as raising of theuser's wrist, if the device is wearable, or other movement indicativethat the user is viewing the display). Advantageously, this featureenables the device to display a different image each time the display isviewed, thereby providing the user with a customized display at eachviewing and enhancing the user interaction with the device. As describedabove, a user movement of the device could be detected, for example, byusing an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motionsensor (e.g., 538), and/or a combination thereof.

In some embodiments, the user may choose to exclude an image from thefolder so that it is no longer selected as a background. In theseexamples, the device may receive data representing a user prohibition ofan image from the folder. Such a prohibition may be received through theuser interface shown in FIG. 12, or it may be received through thefolder containing the two or more images (e.g., the folder may include afeature that allows the user to select more images, drag images into thefolder, delete images from the folder, and/or prohibit an image for useas a background). In response to receiving the data, the device mayprevent the display of the image as a background in response to futureuser input.

FIG. 13A shows exemplary context-specific user interfaces that may beoperated on device 1300. Device 1300 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

A user may wish to view a displayed animation on an electronic device inresponse to an input. Because a user may look at an electronic devicemany times per day, particularly if the user relies on the device fortimekeeping, it may be advantageous to provide the user a differentexperience each time the display is viewed. This keeps the userinterested and engaged with the electronic device.

As shown in FIG. 13A, device 1300 displays user interface screen 1302 inresponse to detecting user input 1304 at 10:09. Screen 1302 includesuser interface object 1306, which indicates the time, as well as userinterface object 1308, which depicts a butterfly. After displayingscreen 1302, device 1300 animates butterfly 1308 by sequentiallydisplaying three animated sequences that are all different from eachother. The first animated sequence is shown by butterfly 1308, whichdepicts the butterfly opening its wings. Next, screen 1310 displays thesecond animated sequence, which depicts butterfly 1314 flying from rightto left on the display. Note that screen 1310 also displays userinterface object 1312, which indicates the time. Finally, screen 1320displays the third animated sequence, which depicts butterfly 1324closing its wings. Screen 1320 again displays user interface object 1322indicating the time.

Later in the day, as shown in FIG. 13B, device 1330 detects a seconduser input 1332. In response, device 1300 accesses data representing thepreviously displayed animated sequence (i.e., the sequence shown bybutterfly 1314). Device 1300 displays screen 1330. Screen 1330 includesuser interface object 1334, which indicates the time is now 2:09, anduser interface object 1336, which depicts a butterfly.

Device 1300 then animates butterfly 1336 by sequentially displayingthree animated sequences. Butterfly 1336 on screen 1330 is animatedusing the same sequence as butterfly 1308 on screen 1302, showing thebutterfly opening its wings. Next, screen 1340 shows butterfly 1334,which is animated to fly from left to right on the display. The animatedsequence of butterfly 1334 is different from the animated sequence ofbutterfly 1314 on screen 1310 (data representing the sequence ofbutterfly 1314 had previously been accessed). This ensures that the userwill view a different animation, as compared to the last user input.This makes the animation appear more realistic and/or engaging to theuser, as this variation imparts a more random, lifelike quality to theanimated user interface object.

Finally, screen 1350 shows butterfly 1354, which is animated using thesame sequence (a butterfly closing its wings) as butterfly 1324 onscreen 1320. Screens 1340 and 1350 also include user interface objects1342 and 1342, respectively, which indicate the time.

FIGS. 13A and 13B show two butterflies (1336 and 1308) that aredisplayed in response to user inputs. Butterfly 1336 is related to 1308,but it need not be identical. In some embodiments, user interface object1336 may be the same as user interface object 1308. In otherembodiments, user interface object 1336 may be an object related, butnot identical, user interface object 1308. For example, these userinterface objects may be animals of the same general type but withdifferent appearances (e.g., different colors, different postures,different species, and so forth).

The animated user interface object may be an animal, such as a butterflyor jellyfish, or it may be a plant, like a flower. In some embodiments,it may be a non-living object, single-celled organism, cartoon, human,and so forth. This context-specific user interface is not limited by theparticular animated user interface object. The animated sequences may bespecific to the displayed objects. For example, a jellyfish may swimacross the screen in various directions, a flower may open, close, or beblown about the wind, and so on.

As illustrated by comparing butterfly 1308 to butterfly 1324, orbutterfly 1336 to butterfly 1354, the third animated sequence may bebased on a reverse of the first animated sequence. For example, if thefirst sequence depicts a butterfly opening its wings, the third sequencemay depict a butterfly closing its wings. Since these sequences bookendthe full animated sequence, this feature imparts a cohesive feel to theentire sequence. In some embodiments, the state of the user interfaceobject at the beginning of the first animated sequence (e.g., butterfly1308 has closed wings, which are then animated to open) corresponds withthe state of the user interface object at the end of the third animatedsequence (e.g., butterfly 1324 is animated to end on closed wings),thereby providing the user with the impression of one seamlessanimation.

A variety of user inputs may serve as the user input to display thescreens exemplified in FIG. 13. In some embodiments, the user input maybe a touch on the display, a rotation of a rotatable input mechanism, adepression of a depressible and rotatable input mechanism, or a swipe onthe display. In some embodiments, the user input may be a user movementof the electronic device (e.g., a movement of the device such as raisingof the user's wrist, if the device is wearable, or other movementindicative that the user is viewing the display). Advantageously, thisfeature enables the device to seemingly display a different animationeach time the display is viewed.

In some embodiments, the user interface object displayed in response touser input may be the same after each input. In some embodiments, theuser interface object could be different each time. For example, a userinterface object may be reflected (e.g., about a horizontal and/or avertical axis), flipped, and/or rotated to create a new user interfaceobject. This is a source of variety for the displayed user interfaceobject and the animated sequences. For example, rotating a single objecthorizontally, vertically, and horizontally and vertically creates fournew objects, which when coupled with an animation that directs themovement of the object creates even more variations. These aspects addcombinatorial possibilities which greatly increase the number ofavailable animations for a single object, thus reducing the number ofpre-programmed animated sequences. It also helps animate objects withfewer intrinsic features and/or movements, such as a jellyfish.

The user may also change the displayed user interface object. Forexample, device 1300 may detect a contact on the touch-sensitivedisplay, and in response, device 1300 may substitute the displayed userinterface object with a second user interface object. This second userinterface object may be related to the first (e.g., the user couldselect an orange butterfly if the previous one was blue).

In some embodiments, as shown in FIGS. 13A and 13B, the user interfaceobject indicating time may be a representation of a digital clock withnumerical indications of an hour and a minute (see, e.g., objects 1306,1312, 1322, 1334, 1342, and 1352). In some embodiments, the userinterface object may display the current time in response to user input.

FIG. 14A shows exemplary context-specific user interfaces that may beoperated on device 1400. Device 1400 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

A user may wish to keep time with an interactive clock face. Forexample, a user may wish to view an animation with each viewing of thedisplay, or view a clock face that changes color, to keep theinteraction with the device interesting. A user may wish to customizethe clock face with a personalized complication, like a monogram, or apersonalized widget for displaying application data.

As shown in FIG. 14A, device 1400 has display 1402 turned off. Inresponse to detecting a user movement of device 1400 (e.g., motion1404), device 1400 displays an animated reveal of a clock face. Onscreen 1410, device 1400 displays clock face outline 1412, which isanimated as if being filled in or drawn in a clockwise manner. On screen1420, device 1400 displays full clock face outline 1422 and hour handand minute hand 1424. On screen 1430, device 1400 displays full clockface outline 1432, hour hand and minute hand 1434, and hour indications1436 and 1438 (indicating the 12 o'clock and 1 o'clock hours,respectively). These hour indications are progressively displayed in aclockwise direction, as shown by comparing screens 1430 and 1440.

On screen 1440, device 1400 displays clock face outline 1442, hour andminute hand 1444, and twelve hour indications, as represented by 12o'clock indication 1446. On screen 1450, device 1400 displays clock faceoutline 1452, hour and minute hand 1454, twelve hour indications (asrepresented by 12 o'clock indication 1456), minute indications 1458, andmonogram 1460, which is described in greater detail below. Therefore, asexemplified in FIG. 14, the clock face is animated to progressivelyreveal its features.

Two types of hour indications are depicted in FIG. 14A: numerical hourindications (e.g., 3, 6, 9, and 12, as indicated by hour indications1436, 1446, and 1456) and symbolic hour indications (e.g., the tickmarks displayed between the numerical indications on screens 1440 and1450). Either type of indication may be used, alone or in combination.Any type of symbol may be used as an hour indications; the positionaround the clock face, rather than the symbol itself, conveys to theuser which hour is indicated. The numbers of hour indications and/orminute indications (or lack thereof) may further be customized by theuser, which will be explained in greater detail below.

FIG. 14A shows that one or more hour indications may be progressivelydisplayed in a clockwise manner (e.g., they may appear sequentially in aclockwise direction, as depicted on screens 1430 and 1440). Similarly,the clock outline may optionally appear in a clockwise direction. Thishelps to orient the user. Optionally, the minute indications may appearprogressively in a clockwise manner. The hour hand and the minute hand(and, optionally, a seconds hand) may be animated as well, such asradially (e.g., starting from the center of the clock face and appearingto extend outward towards the outline). In some embodiments, the hourand minute hand appear first, followed by the hour indications, then theminute indications. In some embodiments, the clock face shows currenttime.

In some embodiments, the clock face may include a color. Features suchas the background of the clock face, clock face outline, seconds hand,hour indication(s), minute indication(s), hour hand, minute hand, and soforth may be displayed in any color. In some embodiments, device 1400updates a color displayed on the clock face over time by continuouslychanging the color, so that the user perceives time passing throughcolor change. This color may be, e.g., a background color, the color ofthe clock face itself, and/or the color of the seconds hand (e.g., theentire seconds hand, or a portion of the seconds hand, such as apointer, dot, or other optional feature). As an illustrative example,the color may cycle through a gradient of colors, with the full cyclelasting a minute, an hour, a day, etc.

In some embodiments, device 1400 may detect a user movement of thedevice. As described above, a user movement of the device could bedetected, for example, by using an accelerometer (e.g., 534), agyroscope (e.g., 536), a motion sensor (e.g., 538), and/or a combinationthereof. A user movement of the electronic device could includemovements such as a movement of the device such as raising of the user'swrist, if the device is wearable, or other movement indicative that theuser is viewing the display. In response to detecting the user movement,device 1400 may display a different color (e.g., a background color, thecolor of the clock face itself, and/or the color of the seconds hand).In some embodiments, this feature may be used to allow the user tochange a static color displayed on the clock face. In other embodiments,this feature may be used to allow the user to change a continuouslychanging color, as exemplified above.

In some embodiments, device 1400 may display a complication on the clockface (e.g., within the clock face itself, or adjacent to the clock faceon the display). As used here, consistent with its accepted meaning inart, a complication refers to any clock face feature other than thoseused to indicate the hours and minutes of a time (e.g., clock hands orhour/minute indications). For example, an affordance may be displayed asa clock face. As will be described in greater detail below, theaffordance may represent an application, and in response to detecting acontact on the affordance, device 1400 may launch the applicationrepresented by the affordance.

Returning now to FIG. 14A, in some embodiments, a monogram may bedisplayed as a complication. Screen 1450 shows monogram affordance 1460displayed as a clock face complication. Device 1400 may receive datarepresenting a name, and in response to receiving the data, generate amonogram and display the monogram as affordance 1460 (in this example,“MJ”). Device 1400 may receive this data from one or more sources, suchas a saved contact entry, a V-card, an image containing a monogram(e.g., an image taken or uploaded by a user), and so forth. In someembodiments, device 1400 has a user interface for monogram editing,which may be a feature of the user interface described in FIG. 14, aseparate user interface on device 1400, or a user interface on anexternal device in wireless communication with device 1400. It is to beappreciated that these aspects (e.g., complications, monograms, and/orcolors) may also be applied to any of the other context-specific userinterfaces described herein. These features provide customizableelements a user may wish to include to personalize one or more clockfaces, thereby improving the user interface by enhancing userinteractability.

FIG. 14B shows exemplary user interface screen 14602 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5). Theelectronic device has a touch-sensitive display (e.g., touchscreen 504).

Users rely on personal electronic devices to keep time throughout theday. It is becoming increasingly desirable to present the user withinteractive user interfaces that promote user interaction with apersonal electronic device. Indicating the time through acharacter-based user interface may enhance a user's interaction with thedevice. Increasing the level of interactivity of a character andimproving the impression of natural motion displayed by a characterimprove the character's lifelike appearance, thereby enhancing andprolonging user interactions with the device. Enabling thecharacter-based interface to not only keep time, but also provideinformation related to other events, further enhances user interactionswith the device by conveying a more lifelike and interactivecharacter-based user interface.

Accordingly, provided herein are context-specific user interfaces thatinclude a character user interface object. A user may wish for suchcharacter-based user interface objects to adopt a more natural andlifelike appearance. Further, a user may wish for the character-baseduser interface object to act in a more dynamic manner, to interact withthe user, and/or to provide event-related information to a user.

Device 14000 may display a character user interface object such ascharacter user interface object 14604 on the display. Character userinterface object 14604 has representations of limbs 14606 and 14608. Asshown on user interface screen 14602, character user interface object14604 may indicate a time, for example 7:50, through the positions oflimbs 14606 and 14608.

A character user interface object may include any representation of acharacter, for example a human or anthropomorphized character. In someembodiments, a character may be a cartoon figure. In some embodiments, acharacter may be a realistic figure. In some embodiments, a charactermay be a human, animal, plant, other organism, or other object. In someembodiments a character may be a popularized character, such as acartoon character.

Character user interface object 14604 may indicate time by indicating anhour with a first limb (e.g., limb 14606) and by indicating a minutewith a second limb (e.g., limb 14608). In some embodiments, thecharacter user interface object may be a static image that is updatablefor different times. In some embodiments, the character user interfaceobject may be animated and may depict movement. For example, thecharacter user interface object may be animated to represent blinking ofeyes, shifting its weight, and/or changing an expression (e.g., facialexpression).

As described herein, a character user interface object may indicate atime through varying degrees of precision. As shown in FIG. 14B, a userinterface screen may include one or more numerical indications of timevalues, i.e., numbers that indicate hour, minute, or second values on aclock face. However, since users are accustomed to perceiving clockfaces, numerical indications of time values are optional, since therelative positioning of two objects resembling the hands of a clock mayindicate an approximate time even without such numerical indications.

Any of the user interface screens described herein may further includeone or more complications, such as indications of a date, a stopwatch, achronograph, an alarm, and the like.

In addition, limbs of a character user interface object may indicatetime to a user in various ways. For example, a limb (e.g., an arm or aleg) may indicate a time by its relative position on the display, or by“pointing” to a position on the display along a vector. A limb may alsoindicate a time by displaying an indicator of direction, such as arepresentation of a finger that indicates a position on the displaycorresponding to a time, either through its relative position or bypointing along a vector, as described above. A limb need not be precisein indicating a time.

Device 14000 may update the character user interface object to indicatea second time by reversing the roles of the first and second limbs,i.e., by indicating a second hour with the second limb and a secondminute with the first limb. For example, FIG. 14B shows user interfacescreen 14610 that device 14000 may display. User interface screen 14610includes character user interface object 14612. Character user interfaceobject 14612 may be the same character user interface object ascharacter user interface object 14604 but representing a different time.

As shown on user interface screen 14610, character user interface object14612 is indicating a time, for example 8:20, through the positions oflimbs 14614 and 14616. Comparing character user interface object 14604and 14612, both have a first limb (limb 14606 and limb 14614,respectively) and a second limb (limb 14608 and limb 14616,respectively). However, character user interface object 14604's firstlimb (limb 14606) is indicating an hour, whereas character userinterface object 14612's first limb (limb 14614) is indicating a minute.Similarly, character user interface object 14604's second limb (limb14608) is indicating a minute, whereas character user interface object14612's second limb (limb 14616) is indicating an hour.

In some embodiments, device 14000 may update the user interface objectto indicate a second time by extending the first limb and retracting thesecond limb. As a user may be accustomed to a standard clock face,wherein the hour hand is shorter than the minute hand, altering theextension and/or retraction of the limbs when reversing their roles maymake it easier for the user to keep track of the indicated times.

Allowing a character user interface object to indicate time using limbswith reversible roles increases the flexibility for displaying thecharacter user interface object by allowing the character to maintain anatural appearance at all times. Otherwise, if the roles of the limbswere fixed, the character might contort in an awkward way at certaintimes of day, for example, between 12:30 and 12:40. Enabling thecharacter to switch roles of the limbs affords more options forcharacter postures and positions that may represent a more naturalappearance, thereby enhancing the user's interactions with the device byportraying a more lifelike character user interface object.

Turning now to FIG. 14C, a user may wish to interact with a morenatural-looking character user interface object. If a character userinterface object indicates time with a limb that is always moving from afixed position or role, this diminishes the natural appearance of thecharacter because the range of motions and/or postures for the characteris restricted. This can lead awkward postures and/or monotonouscharacter appearance. A limb may indicate time via animationsrepresenting free movement from both endpoints of the limb, rather thana representation of rotation about an axis whereby one endpoint isalways fixed, making the character user interface object appear morenatural at different times of day.

It is understood that descriptions of mechanical motions (e.g., limbmotion) used herein encompass displaying representations or simulationsof mechanical motion.

FIG. 14C shows exemplary user interface screen 14702 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).

Device 14000 may display a character user interface object such ascharacter user interface object 14704 on the display. Character userinterface object 14704 has a representation of a limb 14706. As shown onuser interface screen 14702, character user interface object 14704 mayindicate a time, for example an hour such as 12, through the position oflimb 14706. In some embodiments, the character user interface object maybe a static image that is updatable for different times. In someembodiments, the character user interface object may be animated and maydepict movement.

Limb 14706 has a first endpoint 14708 at a first position that serves asa representation of an axis of rotation for limb 14706. That is, theposition of limb 14706 may be displayed or animated so as to representrotation about endpoint 14708 to display different times of day. Limb14706 also has a second endpoint 14710 at a second position thatindicates a time value. In some embodiments, a time value may be anhour, a minute, and/or a second.

Device 14000 may update character user interface object 14704 toindicate a second time value by moving first endpoint 14708 to a thirdposition, and moving second endpoint 14710 to a fourth position toindicate a second time value. Importantly, while first endpoint 14708serves as an axis of rotation for limb 14706, first endpoint 14708itself may also move to indicate time. Therefore, limb 14706 is able toadopt more natural postures because its positioning is afforded moreflexibility. This enhances the lifelike appearance of the character.

As an example, user interface screen 14720 shows character userinterface object 14722 with limb 14724 having first endpoint 14726 andsecond endpoint 14728. Character user interface object 14722 may be anupdated display of character user interface object 14704. Comparing userinterface screens 14702 and 14720, in particular limb 14706 and limb14724, the position of the first endpoint has been updated, as reflectedby the positions of first endpoints 14708 and 14726. First endpoint14726 is at the third position, and second endpoint 14728 is at a fourthposition to indicate the second time. As shown on user interface screens14702 and 14720, limb 14706 has been updated to limb 14724 by (i) movingthe position of first endpoint and (ii) rotating the limb at the axis ofrotation.

In some embodiments, a character user interface object may include arepresentation of a second limb, such as second limb 14712. Like thefirst limb, second limb 14712 also has a first endpoint 14714 that is anaxis of rotation for second limb 14712 and a second endpoint 14716. Theposition of second endpoint 14716 may indicate a third time value. Forexample, limb 14706 may indicate an hour value and limb 14712 mayindicate a minute value. Device 14000 may update character userinterface object 14704 to indicate a fourth time value by moving firstendpoint 14714 of the second limb 14712 to a third position, and bymoving second endpoint 14716 to a fourth position to indicate a secondtime value. This is depicted on user interface screen 14720, whichdepicts second limb 14730 with first endpoint 14732 at the thirdposition and second endpoint 14734 at the fourth position.

As described above, first and second limbs of a character user interfaceobject may each have two endpoints that may each change their position.In some embodiments, the first limb is connected to a torso at a firstshoulder, and the second limb is connected to the torso at a secondshoulder. In some embodiments, the torso connects the movements of eachlimb by each shoulder, such that a position of one shoulder may affect aposition of the other shoulder. This feature adds to the lifelike andnatural appearance of the character by coordinating or otherwiseinter-relating the movements of both limbs, as with a living body.

FIG. 14D shows exemplary user interface screen 14802 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).

Device 14000 may display a character user interface object such ascharacter user interface object 14804 on the display. Character userinterface object 14804 has a representation of a limb 14806. As shown onuser interface screen 14802, character user interface object 14804 mayindicate a time, for example an hour such as 12, through the position oflimb 14806.

Limb 14806 has a first segment 14808 with a first endpoint 14810 at oneend and a joint 14812 at the other. First endpoint 14810 has a firstposition. Limb 14806 also has a second segment 14814 with a secondendpoint 14816 at one end and joint 14812 at the other. Therefore, firstsegment 14808 and second segment 14814 connect at joint 14812, which isan axis of rotation for second segment 14814. Second endpoint 14816 atthe end of second segment 14814 (and hence, at one end of limb 14806)has a second position and indicates a first time value, for example anhour such as 12.

Device 14000 may update character user interface object 14804 toindicate a second time value by moving second endpoint 14814 along theaxis of rotation to a third position to indicate the second time.Described in anthropomorphic terms, limb 14806 has representations of anupper arm 14808 and a forearm 14814 joined at an elbow 14812. Forearm14814 may rotate at the elbow 14812 to indicate a different time. Addinga joint to a limb that indicates time is analogous to a hand of a clock,except that the arm is more natural looking than a clock hand because itincludes a joint. Further, the joint enhances the potential range ofmotions that may be depicted by the limb.

User interface screen 14820 illustrates this by displaying characteruser interface object 14822 with limb 14824. In some embodiments,character user interface object may be the same object as character userinterface object 14804 but in a different posture. Limb 14824 has afirst endpoint 14826, first segment 14828, and joint 14830. Joint 14830is connected to second segment 14832, which has second endpoint 14824.As demonstrated by comparing the features of character user interfaceobjects 14804 and 14822, second endpoint 14834 is at a differentposition than second endpoint 14816, thus indicating a different time.This change in position is accomplished by rotating the second segmentat the joint.

In some embodiments, moving the second endpoint may include depictingstatic images of the second endpoint at the first and third positions.In some embodiments, moving the second endpoint may include animatingthe character user interface object to translate the motion of thesecond endpoint on-screen.

In some embodiments, updating the character user interface object mayinclude moving the first endpoint. As shown by user interface screen14802 to user interface screen 14820, first endpoint 14810 may be movedto change the display of time, e.g., as shown by first endpoint 14826.Therefore, the character user interface object may have a limb that, inthe arm analogy above, may rotate the upper arm at the shoulder, maymove the shoulder itself, and may rotate the forearm at the elbow.

These features allow the character user interface object to assume awider range of natural and lifelike postures with which to indicatetime. If these features are animated on-screen, this allows thecharacter to simulate the motion of a moving figure such as a person.This greatly improves user interaction with and connection to the deviceby more accurately simulating a moving figure like a person. It allowsfor both subtle and dynamic movements, giving the character a widerrange of expressions that help simulate a personality of the character.Therefore, the character ceases to be a simple aggregation of twocharacter-like clock hands that can only tell time and becomes more likean actual character that can express a personality, thereby enhancingthe user's experiences with the device.

In some embodiments, the character user interface object (e.g.,character user interface object 14804 and/or 14822) also includes arepresentation of a second limb, such as second limb 14818 as shown onuser interface screen 14802 or second limb 14836 as shown on userinterface screen 14820. As described above in reference to the firstlimb, a second limb may include a first segment connecting a firstendpoint of the second limb to a joint and a second segment connecting asecond segment to the joint. The first endpoint of the second limb maybe at a first position, and the second endpoint of the second segmentmay be at a second position. The joint may serve as an axis of rotationfor the second segment, which may indicate a third time value. Device14000 may update the character user interface object by moving thesecond endpoint of the second limb along the axis of rotation at thejoint to indicate a fourth time value.

In some embodiments, the first limb indicates an hour and the secondlimb indicates a minute. In some embodiments, the first limb indicates aminute and the second limb indicates an hour. The first limb and thesecond limb may be distinguished, for example, by length, as withtraditional clock hands. The first limb and the second limb may bedistinguished, for example, by the distance between the first and secondendpoints. For example, one limb may be bent or the shoulder may bepositioned such that, even though it may not be shorter than anotherlimb, it appears shorter or otherwise distinct from another limb. Thefirst limb and the second limb may be distinguished, for example, by thedistance between the second endpoint and another object on the display,such as a numerical indication of time.

In some embodiments, updating the character user interface object toindicate the second time may include animating the character userinterface object by translating the first endpoint on-screen. Forexample, the character may appear to move one or both shoulders. In someembodiments, the movement or position of one shoulder may affect themovement or position of another shoulder, simulating the connectedmotion of an actual figure such as a human.

In some embodiments, updating the character user interface object toindicate the second time may include animating the character userinterface object by rotating the second segment at the joint on-screen.For example, the second segment may rotate at the joint like a forearm.

In some embodiments, the character user interface object may alsotranslate on-screen, for example towards a center of the display.

FIG. 14E shows exemplary user interface screen 14902 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 14904 on the display. User interfacescreen 14902 shows the translation of the character by sequentialdisplays of character user interface object 14904 at two differentlocations, first at location 14906 and then at location 14908. Characteruser interface object 14904 is closer to the center of the display atlocation 14908, thus simulating motion in the right-to-left direction asshown in FIG. 14E. Motion such as this may be used, for example, whenthe user initiates an interaction with the device or looks at thedevice, which prompts the character to move to the center of the displayand indicate a time.

In some embodiments, translating the character user interface object mayinclude animating the character user interface object to representwalking, for example to the center of the display. Character userinterface object 14904 illustrates this by depicting a character withlegs and a torso. The different positions and postures represented bythe legs and the torso of character user interface object 14904 atlocations 14906 and 14908 represent walking. For example, in response tothe user interacting with the device, the character may be animated towalk naturally onto the screen and then assume a position correspondingto the current time. The user interaction may include activating thescreen, raising the device into a viewing position, pressing a button onthe device that corresponds to activating a watch face, etc.

FIG. 14F shows exemplary user interface screen 15002 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15004 on the display. Device 14000 maychange a visual aspect of the displayed user interface screen tohighlight the character user interface object. FIG. 14F illustrates anexemplary embodiment of this concept. User interface screen 15002includes a spotlight 15006 that highlights character user interfaceobject 15004.

In some embodiments, changing a visual aspect of the display couldinclude one or more of changing the color and/or brightness of the userinterface screen around the character user interface object, displayinga user interface object such as a spotlight, and so forth.

In some embodiments, device 14000 may animate the character userinterface object to represent a response by the character user interfaceobject to the changing of the visual aspect. As shown in the exemplaryembodiment of FIG. 14F, character user interface object 15004 may beanimated to simulate looking at spotlight 15006.

FIG. 14G shows exemplary user interface screen 15102 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15104 on the display. Character userinterface object 15104 may include a representation of a foot 15106. Insome embodiments, character user interface object 15104 includes twolimbs that indicate time values and two legs, at least one of which mayinclude a foot.

In some embodiments, device 14000 may animate the foot to indicatepassage of time. As shown on user interface screens 15102 and 15110,character user interface objects 15104 and 15112 include a foot (15106and 15114, respectively). The different positions of feet 15106 and15114 (different with respect to the position on the display and/ortheir posture within the character user interface object) depict thisanimation. For example, the character may be animated to simulate amotion of the foot, such as tapping. This may have a regular orirregular timing. In some embodiments, the foot is animated to move at aregular interval, such as once every second. When coupled with twolimbs, this allows the character user interface object to depict, forexample, hour, minute, and second time values.

In some embodiments, the first time and the second time depicted by thecharacter user interface object are the same. In other words, thecharacter user interface object may move by shifting a limb or anyendpoint of a limb without depicting a different time. This allows thecharacter to shift posture without changing the indicated time.

In some embodiments, the display may include one or more numericalindications of time. For example, the display may include arepresentation of a circular clock face with a character user interfaceobject in the center encircled by numerical indicators, as with a clock.

The features described above allow a character user interface object toappear more natural and lifelike by adopting a wider range of naturalmotions while indicating a time. A user may wish to view representationsof other events by the character user interface object. Allowing thecharacter user interface object to react to external stimuli or internalsystem events portrays a more interactive character, thus depicting acloser representation of a personality. The enhanced interactivity ofthe character further improves the user's interactions with the deviceby providing additional notification that an event has occurred, theoccurrence of which may not have been as apparent otherwise. A characteruser interface object may serve to supply notifications, reminders,and/or other information a user may wish to access from a personalelectronic device, but the use of a character provides an interactivepersonality that the device may use to supply these items. Further,making the character responsive to internal system events (e.g.,calendar events and the like) means the character is not strictlylimited to responding to external user input. Put another way, thecharacter appears to have a more lifelike personality because itresponds to events not directly prompted by the immediate actions of theuser.

FIG. 14H shows exemplary user interface screen 15202 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15204 on the display. Character userinterface object 15204 indicates time as described above.

Device 14000 may receive first data indicative of an event. Device 14000may determine whether the event meets a condition. In accordance withthe determination that the event meets the condition, device 14000 mayupdate character user interface object 15204 by changing a visual aspectof the character user interface object.

In some embodiments, after updating the displayed character userinterface object, the character user interface object still indicatestime. For example, the appearance or posture of the character may bealtered, but the character still indicates time.

In some embodiments, after updating the displayed character userinterface object, the character user interface object no longer onlyindicates time. For example, the character may adopt a posture, assume afacial expression, or use its limbs for a function other than indicatingtime, such as conveying a meaning related to the event and/or thecondition.

In some embodiments, the first data indicates a calendar event. Device14000 may receive data indicating a calendar event, for example, byobtaining data representing the event from a calendar application ondevice 14000. In this example, the condition may correspond to aduration of the calendar event. Determining whether the event meets thecondition may include determining whether a current time is within theduration of the calendar event. For example, device 14000 may obtain acurrent time and determine whether the current time is within a durationof the calendar event (e.g., during the calendar event, or substantiallycontemporaneous with the calendar event but slightly preceding orslightly delayed after it).

An exemplary embodiment is shown on user interface screen 15202. In someembodiments, the calendar event is a birthday. In some embodiments, thebirthday is a user's birthday. In some embodiments, updating thedisplayed character user interface object may include animating thecharacter user interface object to display a birthday greeting.Character user interface object 15204 is animated to display festive hat15206 and birthday banner 15208. This animation serves to notify theuser of a birthday while making the character more interactive.Importantly, the character may change a visual aspect, such as bydisplaying a birthday greeting, without immediate input by the user,thus giving the impression that the character is able to act moreautonomously, as with a personality. In some embodiments, themodification of the character is an indication of some important eventrelated to one of the user's contacts, such as their birthday,anniversary, etc.

An exemplary embodiment is shown on user interface screen 15210. In someembodiments, the calendar event is a holiday. In some embodiments,updating the displayed character user interface object may includechanging a visual aspect of the character user interface object toreflect the holiday. In this example, character user interface object15212 depicts this through Santa Claus hat 15214. This animation servesto notify the user of the holiday while making the character moreinteractive and decreasing the monotony of character appearance. Otherexamples of holidays besides Christmas may include New Year's Eve or NewYear's Day, Thanksgiving, Hanukkah, the 4^(th) of July, St. Patrick'sDay, Valentine's Day, and the like.

In some embodiments, device 14000 may receive data indicating a userpreference, such as a user's favorite sports team. In accordance withreceiving the data, device 14000 may update character user interfaceobject 15204 by changing a visual aspect of the character user interfaceobject to reflect the sports team. For example, the appearance of thecharacter user interface object may be updated to portray the characteruser interface object wearing a uniform or other paraphernaliarepresenting the sports team (e.g., a hat, jersey, uniform, or otherrepresentation include a logo, icon, or text representing the sportsteam). The display may also be updated to include with the characteruser interface object a second user interface object representing asports object associated with the team's sport (e.g., a baseball batand/or baseball, football, basketball, soccer ball, hockey stick and/orhockey puck, checkered flag, and so forth). The character may be updatedin accordance with a determination that the team is playing that day orat that time, or in accordance with a determination that the user isgoing to attend an event featuring the team. The determination that theuser is going to attend an event featuring the team may be made throughan analysis of the user's calendar events or through a determinationthat an electronic ticket for an event is present on the electronicdevice or a paired electronic device. It is understood that a user'sfavorite sports team is merely an exemplary user preference, and otheruser preferences such as a representation of a flag or country are alsocontemplated.

FIG. 14I shows exemplary user interface screen 15302 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15304 on the display. Character userinterface object 15304 indicates time as described above.

Device 14000 may receive data indicating a notification. A notificationmay include, for example, an email, text message, reminder, virtualassistant request, or other such notification. Device 14000 may furtherdisplay the notification, or an affordance or user interface objectrepresenting receipt and/or a content of the notification, on userinterface screen 15302, as depicted by notification 15306. Device 14000may animate character user interface object 15304 to react tonotification 15306. For example, as shown on user interface screen15302, character user interface screen 15304 may appear to look atnotification 15306. This may include, for example, a change in posturesuch that the character faces the notification, or a change in theappearance of the character, such as a face, to indicate looking in thedirection of the notification. Again, by providing this change inposture or change in the character's focus, the user may be notified ofan incoming alert or event that may otherwise have been less apparent.

FIG. 14J shows exemplary user interface screen 15402 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15404 on the display. Character userinterface object 15404 indicates time as described above.

Device 14000 may receive first data indicating a time of day. A time ofday could include a current time. Device 14000 may determine that thetime of day meets a condition, such as by determining whether the timeof day is within the nighttime portion of the day. Device 14000 maychange a visual aspect of character user interface object 15404 torepresent nighttime. As shown in user interface screen 15402, characteruser interface object 15404 represents nighttime by depicting a yawn andholding candle 15406. In some embodiments, character user interfaceobject 15404 may be altered to depict wearing clothing associated withnighttime, such as pajamas. In some embodiments, the character interfaceobject is modified to yawn or wear pajamas in accordance with adetermination that the user should go to sleep. The determination may bebased on, for example, any of a preset time, recognition of a pattern ofthe user's sleep, indication of an early event on the next day'scalendar, recognition that the user has been active for longer than apredetermined time, etc.

FIG. 14K shows exemplary user interface screen 15502 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15504 on the display. Character userinterface object 15504 indicates time as described above.

Device 14000 may receive data indicating a current time. Device 14000may determine whether the current time corresponds to an hour on thehour (for example, 1:00, 2:00, and so forth). Device 14000 may determinewhether the current time is an hour on the hour and if so, animate thecharacter user interface object to announce the hour on the hour for oneor more hours. As shown in user interface screen 15502, character userinterface object 15504 announces the current hour by depicting musicalnote 15506. In some embodiments, the announcement of the hour couldinclude a visual depiction of an announcement, such as by displaying auser interface object. In some embodiments, the announcement of an hourcould include a sound such as a whistle, chime, one or more spokenwords, or a bell toll.

FIG. 14L shows exemplary user interface screen 15602 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15604 on the display. Character userinterface object 15604 indicates time as described above.

Device 14000 may receive data indicating current or forecasted weather.To receive data indicating current or forecasted weather, device 14000may retrieve weather information from an external server. In someembodiments, device 14000 may retrieve weather information from aweather service, such as The Weather Channel, Accuweather, The NationalWeather Service, Yahoo!™ Weather, Weather Underground, and the like.

Device 14000 may determine whether the current or forecasted weathercorresponds to one or more designated weather conditions. Designatedweather conditions may be system-designated and may include favorableweather conditions such as sunshine or inclement weather conditions suchas rain, thunderstorms, wind, snow, and so forth. If device 14000determines that the current or forecasted weather corresponds to one ormore designated weather conditions, device 14000 may update thecharacter user interface object to reflect the current or forecastedweather. For example, as shown in FIG. 14L, user interface screen 15602includes character user interface object 15604 with umbrella 15606, aswell as raindrops 15608. In some embodiments, device 14000 may display auser interface object to reflect the designated weather condition. Insome embodiments, the character user interface object may be animated toreact to the user interface object reflective of a designated weathercondition. As another example, user interface screen 15610 displayscharacter user interface object 15612 with sunglasses 15614 andsurfboard 15616, as well as sun 15618.

FIG. 14M shows exemplary user interface screen 15702 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15704 on the display. Character userinterface object 15704 indicates time as described above.

Device 14000 may receive data indicating a second electronic device.Device 14000 may determine whether the data corresponds to a thresholdproximity of the second electronic device to device 14000. If so, device14000 may update character user interface object 15704 by animating thecharacter user interface object to react to the second electronicdevice. As shown in user interface screen 15702, character userinterface object 15704 may depict thumbs up 15706 or smile 15708. Insome embodiments, the posture of the character user interface object maybe updated to reflect the proximity and/or direction of the seconddevice. For example, the character user interface object may react inthe direction of the device or be reflected on the display. In someembodiments, data indicating a second electronic device may be providedthrough a server, which may provide the location of the user's contactsthat have agreed to provide their location data, such as Find MyFriends. Data indicating a second electronic device may also be providedthrough a local network, for example, a recognition that one of theuser's contacts has joined the same WiFi network. Data indicating asecond electronic device may also be provided by the second electronicdevice itself, such as the second electronic device announcing itselfthrough Bluetooth, Near Field Communication, etc.

In some embodiments, a device (such as device 14000) displaying acharacter user interface object indicating time may receive dataindicating user activity. For example, the device may include a useractivity monitor (such as a workout monitor), an accelerometer, agyroscope, a motion sensor, and/or a combination thereof. The device maydetermine whether the data indicating user activity is received outsideof a threshold interval after a previous user activity. For example, thedevice may determine whether a threshold period of time has elapsedsince the last data indicating user activity (e.g., the last userworkout). If the device determines that the data indicating useractivity is received outside of the threshold interval after a previoususer activity, the device may animate the character user interfaceobject to reflect inactivity. For example, the character may change anexpression and/or posture to represent boredom, a sedentary or recumbentposture, a sullen or apathetic appearance, and so forth.

FIG. 14N shows exemplary user interface screen 15802 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15804 on the display. Character userinterface object 15804 indicates time as described above.

Device 14000 may receive data indicating user activity. For example, thedevice may include a user activity monitor (such as a workout monitor),an accelerometer, a gyroscope, a motion sensor, and/or a combinationthereof. Device 14000 may determine whether the user activity is currentuser activity, and, if so, animate character user interface object 15804to represent exercise. For example, user interface screen 15802 includescharacter user interface object 15804 and barbell 15806. In someembodiments, device 14000 may animate the character user interfaceobject to depict an activity related to exercise, such as motion,running, weight lifting, swimming, bicycling, pushups, and/or sweat,heavy breathing, or any other signs of physical exertion. In someembodiments, the activity monitor may include options for the user toindicate which activity they are going to begin. In these cases thecharacter appearance may be changed to reflect the selected activityoption.

FIG. 14O shows exemplary user interface screen 15902 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15904 on the display. Character userinterface object 15904 indicates time as described above.

Device 14000 may receive data indicating user movement of the device,for example by using an accelerometer, directional sensor (e.g.,compass), gyroscope, motion sensor, and/or a combination thereof, and soforth. Device 14000 may determine whether the data indicating usermovement is received outside of a threshold interval after a previoususer movement. For example, device 14000 may determine whether athreshold period of time has elapsed since the last data indicating usermovement (e.g., picking up the device, a motion indicative of a userwrist movement, and so forth). If device 14000 determines that the dataindicating user movement is received outside of the threshold intervalafter a previous user movement, device 14000 may animate the characteruser interface object to indicate fatigue. For example, user interfaceobject 15904 includes limbs 15906 and 15908. Device 14000 may animatecharacter user interface object 15904 to droop one or more of limbs15906 and 15908. In some embodiments, device 14000 may animate characteruser interface object 15904 to shift position, portray physical effort,and the like.

FIG. 14P shows exemplary user interface screen 16002 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 16004 on the display. Character userinterface object 16004 indicates time as described above.

Device 14000 may receive data indicating a user contact on thetouch-sensitive surface (e.g., a touchscreen). Device 14000 maydetermine whether the user contact corresponds to a user contact oncharacter user interface object 16004. In some embodiments, the usercontact may be on a touchscreen at the position of the character userinterface object. In some embodiments, the user may input information tomanipulate a cursor or other indicator to contact the displayedcharacter user interface object. For example, as shown on user interfacescreen 16002, a user may contact character user interface object 16004with touch 16006.

If device 14000 determines that the user contact corresponds to a usercontact on character user interface object 16004, device 14000 mayanimate character user interface object 16004 to react to the contact.In some embodiments, the reaction may be a specific to the location ofthe contact on the character user interface object. In some embodiments,the reaction may be a general reaction. In some embodiments, thereaction may include, for example, reacting as to tickling, hugging, orother forms of friendly contact. In some embodiments, character userinterface object 16004 may display a second animation distinct from thefirst animation in response to a second user contact.

FIG. 14Q shows exemplary user interface screens 16102 and 16202 thatdevice 14000 can display on its display. In some embodiments, device14000 may be one or more of devices 100 (FIG. 1), 300 (FIG. 3), and/or500 (FIG. 5). Device 14000 may display character user interface object16104 on the display. Character user interface object 16104 indicatestime as described above. As shown in FIG. 14Q, in some embodiments,character user interface object 16104 may depict a facial expression,such as a yawn. In some embodiments, character user interface object16204 may depict speech, such as by presenting text in a displayed userinterface object or affordance representing speech balloon 16206 or athought balloon. Speech may be depicted to visually present anannouncement made by a character user interface object, such as anannouncement of the hour as described above with reference to characteruser interface object 15504 in FIG. 14K.

FIG. 14R shows exemplary user interface screens 16302 and 16402 thatdevice 14000 can display on its display. In some embodiments, device14000 may be one or more of devices 100 (FIG. 1), 300 (FIG. 3), and/or500 (FIG. 5). Device 14000 may display character user interface object16304. Character user interface object 16304 indicates time as describedabove. As shown in FIG. 14R, in some embodiments, character userinterface object 16304 may depict boredom or fatigue, as describedabove. In some embodiments, the character user interface object maydepict attire. For example, character user interface object 16404 maydepict a sports team or a sports object (e.g., baseball 16406 and bat16408), such as those representing the user's favorite sports team, asdescribed above.

FIG. 14S shows exemplary user interface screen 16502 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display character user interface object 16504.Character user interface object 16504 indicates time as described above.As shown in FIG. 14S, in some embodiments, character user interfaceobject 16504 may depict a facial expression, such as blinking, closing,or winking one or more the eyes. The character interface object maychange facial expression at predetermined or random intervals to providean indication to the user that the interface is still active.

FIG. 14T shows exemplary user interface screen 16602 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object on thedisplay. The displayed character user interface object indicates time asdescribed above. As shown in FIG. 14T, in some embodiments, thecharacter user interface object includes one or more second endpoints,such as a second endpoint of a limb and a second endpoint of a secondlimb, as described above. In some embodiments, the second endpoint 16604of a first limb may indicate an hour and be positioned along thecircumference of a first circle 16606. The second endpoint 16608 of asecond limb may indicate a minute and be positioned along thecircumference of a second circle 16610 that encircles the first circle16606 and has a larger circumference than the first circle 16606. Inthis way, the user may distinguish which limb indicates an hour andwhich limb indicates a minute by the relative closeness to an edge ofthe display or to one or more displayed numerical indications of time.

In some embodiments, a device (such as device 14000) may detect a userinput and, in response to detecting the user input, display a characteruser interface object. For example, the display of the device may showanother display or be dark, then display the user interface object onthe screen in response to the user input. In some embodiments, the userinput may be a movement of the device (e.g., picking up the device, amotion indicative of a user wrist movement, and so forth). In someembodiments, the user input may be a touch on the touch-sensitivesurface (e.g., a touchscreen).

2. Editing Context-Specific User Interfaces

The context-specific user interfaces described and illustrated hereinprovide numerous elements and features that a user may customize,depending upon a particular context. As described, these customizableelements enhance the user interfaces, making them more personal andinteractive to the user.

At the same time, a user also wants a device that is easy and intuitiveto use. Providing a multitude of features only serves to frustrate theuser if the user interface does not provide comprehensible ways to editthese features. Described below are user interfaces for editingcontext-specific user interfaces that provide easy and intuitive methodsthat facilitate user customization.

Importantly, it is to be appreciated that, while particular embodimentssuch as clock faces may be described with respect to particular editingfeatures, these editing features may also apply to one or more of theother user interfaces described herein. For example, a method forcustomizing a color of a clock face may be used to change the color of aseconds hand, change an animated object (e.g., a butterfly), or change aclock face background (e.g., a photo or image of a scene). Similarly,methods for customizing complications may be used to add and/or editvarious complications on any clock face, regardless of whether anembodiment of that clock face bearing a particular complication wasdescribed herein. A skilled artisan will recognize that the methodsdescribed below provide user interface functionalities that may beapplied to elements and aspects of various context-specific userinterfaces in numerous combinations, such that each possible combinationwould be impossible to elaborate individually.

It is to be further appreciated that references to a “clock face” withrespect to clock face editing and/or selection as described herein arenot in any way limited to a traditional notion of a “clock face,” e.g.,a circular display with hour indications and one or more hands toindicate time, or a representation of a digital clock. Anycontext-specific user interface with an indication of time describedherein may properly be termed a clock face.

Attention is now directed to FIG. 15. FIG. 15 shows exemplarycontext-specific user interfaces that may be operated on device 1500.Device 1500 may be device 100, 300, or 500 in some embodiments. Theelectronic device has a touch-sensitive display (e.g., touchscreen 504)configured to detect the intensity of contacts. Exemplary components fordetecting the intensity of contacts, as well as techniques for theirdetection, have been referenced and described in greater detail above.

Device 1500 displays user interface screen 1502, which includes clockface 1504. Clock face 1504 also includes complication 1506 that displaysa set of information from a weather application (e.g., current weatherconditions). In this example, the user wishes to change multiple aspectsof clock face 1504. Specifically, the user decides to change the hourindications on clock face 1504 and complication 1506.

The user contacts the touch-sensitive display of device 1500 with touch1508. Touch 1508 has a characteristic intensity above an intensitythreshold, which prompts device 1500 to enter a clock face edit mode,shown on screen 1510. Clock face edit mode allows the user to edit oneor more aspects of a clock face. Device 1500 indicates that the user hasentered clock face edit mode by visually distinguishing the clock face.In this example, screen 1510 shows a smaller version of the display ofscreen 1502 (e.g., 1512), which includes reduced size clock face 1514based on clock face 1504. Reduced size complication 1516, which is basedon complication 1506, is also displayed. This display indicates to theuser that the user is in clock face edit mode while giving the user anindication of what the edited clock face will look like on the display.In some embodiments, a user may be able to select a different clock faceby swiping displayed screen 1510, as described in greater detail belowin reference to FIGS. 16A-C.

Screen 1510 also displays paging affordance 1518. Paging affordances mayindicate where the user is within a sequence of options, as well as howmany options are available in the sequence. In clock face edit mode,paging affordances may indicate which editable aspect of the clock facea user is editing, where this aspect falls within a sequence of editableaspects, and the total number of editable aspects in the sequence (ifclock face selection is available on this screen, paging affordance 1518may depict the currently selected clock face within a sequence ofselectable clock faces and/or clock face options, as described below). Apaging affordance may be advantageous in clock face edit mode to helpthe user navigate the interface and explore all of the editable optionsavailable within each type of clock face.

The user selects the displayed clock face for editing by contacting 1512through touch 1520. In response to detecting touch 1520, device 1500visually indicates an element of the clock face for editing. As shown onscreen 1530, the hour indications have been selected for editing, asindicated by outline 1534 around the position of the hour indications.The other elements of the clock face are still retained, as shown byhour hand and minute hand 1532 and complication 1536.

In this example, three aspects of the clock face are available for userediting. This is depicted by paging affordance 1538. The first editableaspect is the hour indications (e.g., their number and/or appearance).This is relayed to the user by paging affordance 1538. By viewingoutline 1534 in combination with paging affordance 1538, the userrecognizes that the hour indications are the first of three editableaspects of this clock face.

Device 1500 also has rotatable input mechanism 1540. The user may moverotatable input mechanism 1540 to cycle through different options forediting different aspects of the clock face. On screen 1530, the usermay select different options for the hour indications (which arecurrently editable, as depicted by outline 1534) through movement 1542.Advantageously, using a rotatable input mechanism to cycle throughediting options (rather than using, e.g., a touch interaction) frees uptouch interactions with the screen to instead provide otherfunctionalities, thus expanding the interactability of the device. Usinga rotatable input mechanism is also helpful in cases where smallerelements of the display are being edited, as finer-scale touch gesturesmay be difficult on a reduced-size display for users with large fingers.

Also displayed on screen 1530 is positional indicator 1544, shown as acolumn of 9 lines. Positional indicator 1544 is an indicator of acurrent position along a series of positions. This is may be used, forexample, in combination with rotatable input mechanism 1540. On screen1530, positional indicator 1544 indicates to the user the position ofthe currently selected option (e.g., by line 1546) within a series ofall selectable options.

Upon detecting movement 1542, device 1500 displays screen 1550. Inresponse to detecting movement 1542, device 1500 edits the hourindications, in this case by increasing the number of indications andadding numerals. This is shown by indications 1552, still highlighted byoutline 1534. The other elements of the clock face, hour hand and minutehand 1532 and complication 1536, remain the same. Positional indicator1544 has been updated to indicate the position of this hour indicationoption, highlighted by line 1554, within a series of positions of hourindication options.

As indicated by paging affordance 1538, the hour indications are thefirst editable aspect of this clock face within a sequence of editableaspects. The user may select a second editable aspect by swiping thetouch-sensitive display (e.g., swipe 1556). In response to detecting theswipe, device 1500 displays screen 1560. Screen 1560 includes clock face1562, which now has 12 hour indications, including 4 numericalindications, as depicted by hour indications 1552. Note that these hourindications are the hour indications that were selected by the user onthe previous screen (see indications 1552). Paging affordance 1538 hasnow been updated to indicate that editing complications is the secondeditable aspect within the sequence of editable aspects in this clockface.

On screen 1560, complication 1536 is currently editable, as indicated tothe user by outline 1564. Currently, complication 1536 is displayingcurrent weather conditions using information from a weather application.This option is option 3 in a series of options, as indicated by updatedpositional indicator 1544 and line 1566. Positional indicator 1544 letsthe user know that the currently selected feature (i.e., complication1536) is editable by the rotatable input mechanism.

While screen 1560 depicts a single complication, it should be understoodthat multiple complications may be displayed. When multiplecomplications are displayed, a user may select a particular complicationfor editing by contacting the corresponding position of thecomplication. Outline 1564 then transitions from the previously selectedcomplication or element to the currently selected complication orelement and rotatable input mechanism may then be used to edit thecomplication or element at the selected location. This concept isdescribed in greater detail below in reference to FIG. 18C.

It is to be noted that positional indicator 1544 is displayed on screens1530, 1550, and 1560, even though the available options depicted by theindicators are different. A positional indicator may be a universalindicator of options available through a particular type of user input,such as a movement of the rotatable input mechanism. Rather thandisplaying positions within a particular context, such as editing acertain feature or displaying data from a particular application, apositional indicator shows the user positions available through a typeof user input, no matter the particular context in which the user inputis being used. This better indicates to the user which user input shouldbe used for this functionality. In some embodiments, a positionalindicator is displayed on the display at a position adjacent to the userinput for which it is used (e.g., next to the rotatable input mechanismto indicate positions accessible by moving the rotatable inputmechanism).

A positional indicator (e.g., positional indicator 1544) may beresponsive to one or more inputs. For example, as shown in FIG. 15, thepositional indicator 1544 may indicate options available through amovement of the rotatable input mechanism. As described above, the usermay scroll through the available options using movement of the rotatableinput mechanism. However, a user may also wish to scroll through theavailable options using a second type of input, such as a contact (e.g.,a swipe) on the touch-sensitive display. In some embodiments, a userviewing screen 1530 may swipe the touch-sensitive display in a differentdirection than the swipe used for removing a visual indication of afirst element of the clock face for editing and visually indicating asecond element of the clock face for editing (e.g., a downward swipe onthe display). For example, to scroll through the available options shownin FIG. 15, the user may swipe in a substantially horizontal direction(e.g., swipe 1556) to scroll through editable aspects (e.g., with swipesmoving left-to-right resulting in scrolling through the sequence ofeditable aspects in one direction, and swipes moving right-to-leftresulting in scrolling through the sequence of editable aspects in adifferent direction, as depicted by updating the paging affordance1538). In this example, the user may swipe in a substantially verticaldirection (e.g., perpendicular to swipe 1556) to scroll throughavailable options (e.g., with swipes moving downwards resulting inscrolling through the sequence of available options in one direction,and swipes moving upwards resulting in scrolling through the sequence ofavailable options in a different direction, as depicted by updating thepositional indicator 1544). In some embodiments, the user may swipe thedisplay at or near the location of the displayed positional indicator toscroll through the sequence of available options.

In some embodiments, upon detecting the swipe, the device may update anindicator of position (e.g., an indicator of position along a series ofpositions that indicates a position of a currently selected option forthe editable aspect along a series of selectable options for theeditable aspect of the visually indicated element of the clock face) toindicate a second position along the series. In some embodiments, upondetecting the swipe, the device may edit an aspect of the visuallyindicated element of the clock face. In some embodiments, the device mayvisually distinguish the positional indicator (e.g., by changing acolor, size, shape, animation, or other visual aspect) based on the typeof input used to scroll the indicator. For example, in some embodiments,in response to detecting a movement of the rotatable input mechanism,the device may display the positional indicator in a first color (e.g.,green), and in some embodiments, in response to detecting a swipe, thedevice may display the positional indicator in a second color differentfrom the first color (e.g., white).

In clock face edit mode depicted on screen 1560, the user may be able tocycle through different types of information from the weatherapplication, or change the application from which the information isdrawn. In this case, the user moves rotatable input mechanism usingmovement 1568, which causes device 1500 to display screen 1570. Thisupdates complication 1536 to display the current date, which is obtainedfrom a calendar application. This option is indicated within positionalindicator 1544 by line 1572. Note that paging affordance 1538 stillindicates the second position because the user is still engaged inediting complications, the second editable aspect of this clock face. Adetermination that the contact has a characteristic intensity above apredetermined threshold may be user to distinguish the contact fromother gestures, such as a tap or the beginning of a swipe.

Having finished editing the clock face, the user may now exit clock faceselection mode and display the edited clock face on the display. In someembodiments, this may be done by detecting a user contact with acharacteristic intensity above an intensity threshold. In accordancewith a determination that the characteristic intensity is above theintensity threshold, the device may exit clock face edit mode and ceaseto visually distinguish the displayed clock face for editing (e.g., byincreasing the size of the displayed clock face). In some embodiments,in accordance with a determination that the characteristic intensity isabove the intensity threshold, the device may save this edited clockface as a new clock face that is accessible through clock face selectionmode (described below). In accordance with a determination that thecharacteristic intensity is not above the intensity threshold (where theclock face includes an affordance representing an application, and wherethe contact is on the affordance representing the application), thedevice may launch the application represented by the affordance.

In some embodiments, the device may have a rotatable and depressibleinput mechanism (e.g., 506), and in response to detecting a depressionof the rotatable and depressible input mechanism, the device may exitclock face edit mode, display the currently edited clock face, and/orsave the currently edited clock face for later user selection, asdescribed above.

FIG. 15 illustrates an exemplary embodiment of clock face edit mode, buta number of other potential embodiments are possible within the scope ofthe techniques described herein. For example, in FIG. 15, an element wasindicated for editing by visibly distinguishing an outline around theelement (e.g., by displaying a visible outline, or by distinguishing apre-existing outline already visible around the element), as illustratedby outlines 1534 and 1564. In some embodiments, the outline may beanimated to depict a rhythmic expansion and contraction (e.g., animationsimilar to pulsing or breathing). In some embodiments, the elementindicated for editing itself may be animated to depict a rhythmicexpansion and contraction. In some embodiments, the element may beanimated to depict flashing. In some embodiments, a color of the elementmay be changed (e.g., a change in color and/or intensity). Any or all ofthese indications may be used to visually indicate the element that iscurrently editable.

As shown in FIG. 15, movement of a rotatable input mechanism may beemployed as the user input for editing an aspect of the elementindicated for editing. In some embodiments, if an outline is used toindicate the currently editable element, the outline may disappear whenthe rotatable input mechanism is being moved, and reappear when themovement stops. In this way, the user is able to see what the editedelement will look like on the clock face as a whole, without anypossible obstruction or distraction from the outline.

In some embodiments, in response to detecting the movement, the devicemay change a color of the element. This could include, e.g., changing acolor of a clock face background (e.g., substituting a color if theclock face background is a particular color, or selecting a differentimage if the clock face background includes an image), changing a colorof part or all of a seconds hand (if included on the clock face),changing a color of an hour and/or minute indication, and/or changing acolor of a number or colon in the display of a representation of adigital clock. Since a seconds hand is a smaller element than abackground (and therefore may be more difficult for the user toperceive), changing the color of the seconds hand may include ananimated color change. For example, the seconds hand could first changea color of a particular point (e.g., a dot depicted along the secondshand), then propagate this color change in either direction along theseconds hand. Alternatively, the color change could begin at the originof the clock face and propagate outward. Animating a color change,particularly a change of a smaller element of the clock face, may behelpful to draw the user's attention to the color change.

In other embodiments, in response to detecting movement of the rotatableinput mechanism, the device may change an aspect of a complication. Forexample, this could be used to change application data displayed by anapplication complication. In some embodiments, the complication mayindicate a first set of information obtained by an application (e.g.,application data. For example, if the application is a weatherapplication, a set of information could be a forecasted weathercondition, a current temperature, etc.), and upon editing, thecomplication could be updated to indicate a second set of informationfrom the same application (e.g., if the application is a weatherapplication, the display could be edited from showing a currenttemperature to showing current precipitation). In other embodiments,upon editing, the complication could be updated to indicate a set ofinformation from a different application (e.g., if the application is aweather application, the display could be edited from showing weather toshowing data from a calendar application, as illustrated by complication1536).

In other embodiments, in response to detecting movement of the rotatableinput mechanism, the device may change an aspect of display density. Forexample, as illustrated in FIG. 15, this could be used to edit thenumber of visible divisions of time (e.g., the number of displayed hourand/or minute indications, such as numbers 1-12 or other marks/symbolspositioned along the clock face at the hour positions). In response todetecting movement of the rotatable input mechanism, the device mayincrease or decrease the number of visible divisions of time. Asillustrated on screens 1530, 1550, and 1560, this could involve changingthe number of visible divisions (e.g., from 4 to 12) and/or changing thenumber of numerical/symbolic hour indications (e.g., from 0 to 4).

In some embodiments, as illustrated in FIG. 15, an indicator ofpositions along a series of positions may be displayed (e.g., positionalindicator 1544). In response to detecting movement of the rotatableinput mechanism, the device may update the indicator from indicating afirst to indicating a second position along the series of positions. Insome embodiments, the indicated position may reflect a currentlyselected option for the currently editable aspect along a series ofselectable options for the currently editable aspect. As describedabove, in some embodiments, the indicator is displayed on the display ata position adjacent to the rotatable input mechanism, therebystrengthening the user's association between the indicator and theinput. In some embodiments, if the currently editable aspect is color,the device may display a positional indicator that includes a series ofcolors, such that the currently selected color option matches the colorof the position currently indicated by the positional indicator (e.g.,the color could be a similar or identical color). In some embodiments,the number of positions displayed in a position indicator increases ordecreases depending on the number of options for the currently selectededitable aspect.

In some embodiments, upon reaching the last position indicated by thepositional indicator, the device may provide an indication to the userthat the last option has been displayed. For example, the device maydepict a dimming of one or more of the selected element, an outlinearound the selected element, and the positional indicator. In someembodiments, the device may animate one or more of the selected element,an outline around the selected element, and the positional indicator toexpand and contract (e.g., like a rubber band). In some embodiments, thedevice may animate one or more of the selected element, an outlinearound the selected element, and the positional indicator to move on thedisplay (e.g., by bouncing). These features may be advantageous toprovide an indication to the user that the last option in the series ofoptions has been reached.

In some embodiments, a user may select the element on the clock face forediting by contacting the touch-sensitive display at the position of thedisplayed element. In other embodiments, the element may be selected byswiping the touch-sensitive display, or rotating the rotatable inputmechanism. Regardless of the input, selecting a second element forediting may involve removing a visual indication from the previouselement and visually indicating a second element for editing (visuallyindicating may include any or all of the techniques described above).

In some embodiments, if the element selected for editing is indicated byan outline around the element, changing an element for editing couldinvolve translating the outline on-screen away from the first elementand/or translating a visible on-screen in a continuous on-screenmovement towards the second element until the outline is displayedaround the second element.

As illustrated in FIG. 15, clock face edit mode allows the user to altermultiple editable aspects of the clock faces described herein. In someembodiments, in response to detecting a swipe on the touch-sensitivedisplay (e.g., swipe 1556), the device may select a second element ofthe clock face for editing, which in response to detecting another userinput (e.g., a movement of the rotatable input mechanism), may beedited. This allows the user to cycle through different editable aspectsof the displayed clock face, such as colors, number and/or type ofcomplications, and display density.

A user may wish to match a color of a displayed clock face to an image.In some embodiments, the device may receive a user input, and inresponse to receiving the user input, the device may enter a colorselection mode. While in the color selection mode, the device mayreceive data representing an image, and in response to receiving thedata, the device may select a color of the image and update a displayedclock face by changing a color on the clock face (e.g., a clock facebackground, hour and/or minute indication, and/or seconds hand) to matchthe color of the image. In some embodiments, the color selected may havethe greatest prevalence of the colors in the image. This allows the userto further customize a clock face to display a designated color. Forexample, if the user is wearing a blue shirt, the user could take animage of the blue shirt and match the color of the clock face to theshirt. In some embodiments, the data representing the image may beobtained from an image stored on the device, an image stored on anexternal device in wireless communication with the device (e.g., Wi-Fi,Bluetooth™, near field communication (“NFC”), or any of the othercellular and/or other wireless communication techniques describedherein), or an image taken using a camera on the device, such as cameramodule 143 or optical sensor 164.

Having described various context-specific user interfaces and methods ofuser editing thereof, attention is now directed to methods of selectinga context-specific user interface shown in FIGS. 16A-C. Numerousindividual context-specific user interfaces are possible using thetechniques described here. A user may wish to select a particular clockface (e.g., from a saved library of clock faces) or make a new one,depending on a particular context. For example, a user may wish todisplay a particular clock face during working hours to project aprofessional appearance, but change the clock face during the weekend toreflect an interest (such as astronomy, exercise, or photography). Auser may wish for quick access to a stopwatch in one context, whiledesiring an indication of daytime hours in another.

FIG. 16A shows exemplary context-specific user interfaces that may beoperated on device 1600. Device 1600 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504) configured to detect the intensity of contacts.Exemplary components for detecting the intensity of contacts, as well astechniques for their detection, have been referenced and described ingreater detail above.

Device 1600 displays user interface screen 1602, which includes clockface 1604. In this example, the user wishes to switch from clock face1604 to a different clock face. The user contacts the touch-sensitivedisplay of device 1600 with touch 1606. Touch 1606 has a characteristicintensity above an intensity threshold, which prompts device 1600 toenter a clock face selection mode, shown on screen 1610. Clock faceselection mode allows the user to select a clock face.

Device 1600 indicates that the user has entered clock face selectionmode by visually distinguishing the clock face. This is shown on screen1610. Screen 1610 visually distinguishes that the user has entered clockface selection mode by centering reduced size clock face 1612 on thedisplay (reduced size clock face 1612 is based on clock face 1604). Thisindicates to the user that the user is in clock face selection modewhile giving the user an indication of what the clock face will looklike when displayed at full size.

Screen 1610 also includes paging affordance 1614. As described above,paging affordances may indicate where the user is within a sequence ofoptions, as well as how many options are available in the sequence.Paging affordance 1614 indicates to the user that clock face 1612 is thefirst in a series of three selectable clock faces and/or clock faceoptions (e.g., an option to add a new clock face or randomly generate aclock face, as described below). In clock face selection mode, a pagingaffordance may indicate a currently centered clock face and/or clockface option, a position of the currently centered clock face and/orclock face option within a sequence of clock faces and/or clock faceoptions, and a total number of available clock faces and/or clock faceoptions. This helps the user navigate the clock faces and clock faceoptions.

Screen 1610 also includes a partial view of a second clock face, asshown by a partial view of second clock face 1616. In some embodiments,when the device is in clock face selection mode, the device may includea display a partial view of another clock face, or clock face option,particularly the clock face or clock face option next in the sequence(e.g., as indicated by the paging affordance). This further helps theuser understand that additional options are available. In otherembodiments, only one clock face is displayed at any time.

Clock face selection mode may be used to select a clock face for displayas a context-specific user interface, or to select a clock face forediting. Therefore, in some embodiments, when a clock face such as clockface 1612 and/or clock face 1616 is centered on the display, a user maycontact the displayed clock face on the touch-sensitive display toselect the centered clock face for editing and enter into clock faceediting mode (as described above in reference to FIG. 15). In someembodiments, clock face editing mode is entered when the contact has acharacteristic intensity above an intensity threshold. Coupling clockface edit and selection modes in a single interface allows the user toselect different clock faces and edit them quickly and easily.

A user may select a different clock face (for editing or for display asa context-specific user interface) by swiping. Device 1600 detects aswipe on the touch-sensitive display (e.g., swipe 1618). In response todetecting swipe 1618, device 1600 displays screen 1620. Screen 1620includes second clock face 1616 centered on the display (part of secondclock face 1616 was depicted on screen 1610). Screen 1620 also showspaging affordance 1614, which has been updated to indicate that thecurrently centered clock face 1616 is second within the sequence ofclock faces and/or clock face options. Also shown is a partial viewclock face 1612. This helps the user understand the sequence of clockfaces, similar to a paging affordance but with the added benefit ofdisplaying a partial view of the clock faces for user recognition.

To select clock face 1616, the user contacts the touch-sensitive displayon clock face 1616 (e.g., touch 1622). In response to detecting touch1622, device 1600 exits the clock face selection mode and displaysscreen 1630. Screen 1630 includes full-sized clock face 1632, which isbased on clock face 1616. In this example, clock face 1632 is acontext-specific user interface similar to those described in referenceto FIGS. 11A-C and includes affordance 1634 indicating the time of day,user interface object 1636 (a sinusoidal wave indicating a path of theSun through the day), and affordance 1638 representing the Sun.

As described above and illustrated in FIG. 16A, a user may select aclock face from a plurality of clock faces in the device's clock faceselection mode. In some embodiments, at least a first and a second clockface are shown when the device is in clock face selection mode. Theseclock faces may be shown in sequence, but at a reduced size. In someembodiments, one clock face is centered on the display at any time, andthe one or more additional clock faces on the display are shown inpartial view, as depicted by partial views of clock faces 1612 and 1616.Centering a clock face may include includes translating the prior clockface in the sequence on-screen and displaying the prior clock face inpartial view. In other embodiments, only a single clock face isdisplayed on the device at any one time (i.e., no partial views).

In some embodiments, centering a clock face on the display includessimulating a movement of the clock face towards the user on the display,as if it is approaching the user. This helps draw the user's attentionto the clock face while conveying to the user a sense of the clock facesequence.

As depicted by screen 1620, device 1600 may display multiple availableclock faces and/or clock face options in a sequence for selection by theuser. A user may wish to re-order one or more clock faces within thesequence. Therefore, device 1600 may provide a clock face rearrangementmode to allow the user to select a particular clock face and change itsorder within the sequence of available clock faces and/or clock faceoptions. In some embodiments, a user may contact the touch-sensitivedisplay on a clock face (e.g., clock face 1616) and maintain the contactbeyond a threshold interval (e.g., a “press and hold”-type user input).In response to detecting the contact, and in accordance with adetermination that the contact exceeds a predetermined threshold, device1600 may enter a clock face rearrangement mode. Device 1600 mayhighlight, outline, animate, or otherwise visually distinguish the clockface to indicate to the user that device 1600 has entered clock facerearrangement mode, and that the clock face has been selected forrearrangement. In some embodiments, while continuing to receive the usercontact, device 1600 may detect movement of the user contact from afirst position within the sequence of displayed clock faces and/or clockface options to a second position, which is different from the firstposition, without a break in contact of the user contact on thetouch-sensitive display. In other embodiments, the contact comprisingthe movement from a first position within the sequence of displayedclock faces and/or clock face options to a second position, which isdifferent from the first position, without a break in contact of theuser contact on the touch-sensitive display may be a separate contactsubsequent to entry into clock face rearrangement mode. In response todetecting the contact at the second position, device 1600 may translatethe clock face on-screen from the first position to the second position.Optionally, other partial or complete clock faces and/or clock faceoptions on the display may be moved accordingly to accommodate the newposition of the user-selected clock face. A user may then cease thecontact to select the second position as the new position for the clockface within the sequence of displayed clock faces and/or clock faceoptions. In some embodiments, device 1600 may exit clock facerearrangement mode in response to detecting the break in contact on thetouch-sensitive display after the position of at least one clock facehas been rearranged. In other embodiments, in response to detecting auser input subsequent to the break in contact on the touch-sensitivedisplay (e.g., a depression of a rotatable and depressible inputmechanism such as 506), device 1600 may exit clock face rearrangementmode. In some embodiments, upon exiting clock face rearrangement mode,device 1600 may re-enter clock face selection mode.

In addition to selecting an existing context-specific user interface, auser may also wish to add a new one. FIG. 16B illustrates an exemplaryuser interface for generating a new clock face. Shown on FIG. 16B isdevice 1600, which displays screen 1640. Screen 1640 displays clock face1642 and paging affordance 1644, which indicates to the user that thecurrently centered clock face is the first in a sequence of threeselectable clock faces and/or clock face options. Screen 1640 alsodisplays a partial view of a clock face generation affordance (e.g.,1646).

In this example, the user swipes the display (e.g., swipe 1648), and inresponse to detecting the swipe, device 1600 displays a full view ofclock face generation affordance 1646 centered on screen 1650. In someembodiments, as depicted by affordance 1646, a clock face generationaffordance may include a plus sign (or other text and/or symbol) toconvey to the user that, upon activation of affordance 1646, device 1600will generate a new clock face.

Note that screen 1650 also displays a partial view of previouslydisplayed clock face 1642. This partial view of 1642 and updated pagingaffordance 1644 (updated to indicate that clock face generation is thesecond available user interface in the sequence) help orient the userwithin the sequence of available clock faces and/or clock face options.Further note that the partial view of clock face generation affordance1646 on screen 1640 indicates to the user that a swipe will centeraffordance 1646 on the display (e.g., as displayed on screen 1650) foruser activation.

A user may activate affordance 1646, for example by contactingaffordance 1646 on the touch-sensitive display (e.g., touch 1652). Inresponse to detecting the contact, device 1600 displays screen 1660,which includes newly generated clock face 1662 centered on the display.As shown on screen 1660, new clock face 1662 includes affordance 1664,which displays the current date (e.g., obtained from a calendarapplication), and affordance 1666, which displays the current weatherconditions (e.g., obtained from a weather application).

In response to detecting an activation of affordance 1646, in someembodiments, the device remains in clock face selection mode aftercentering the displayed new clock face. In other embodiments, uponcentering the newly generated clock face on the display, the deviceenters into clock face edit mode, as described above. This allows theuser to edit one or more aspects of the newly generated clock face. Insome embodiments, the device exits clock face selection mode and centersthe new clock face as a full-size clock face on the display.

It is to be appreciated that, while new clock face 1662 depicts arepresentation of an analog clock, any of the context-specific userinterfaces described herein (with any of the optional features describedherein) may be a new clock face generated in response to activating theclock face generation affordance. In some embodiments, a new clock facemay have a different customizable aspect, as compared to existing clockfaces on the device. For example, if the user already has a clock facethat includes a blue seconds hand, the device may generate a new clockface that includes a red seconds hand. This helps the user explore theoptions available for context-specific user interfaces described herein,thus enhancing the user interface by increasing variety.

In addition to selecting an existing context-specific user interface orgenerating a new context-specific user interface, a user may also wishto create a random context-specific user interface. FIG. 16C illustratesan exemplary user interface for generating a random clock face. Shown onFIG. 16C is device 1600, which displays screen 1670. Screen 1670displays clock face 1672 and paging affordance 1674, which indicates tothe user that the currently centered clock face is the first in asequence of three selectable clock faces and/or clock face options.Screen 1670 also displays a partial view of a random clock facegeneration affordance (e.g., 1676).

In this example, the user swipes the display (e.g., swipe 1678), and inresponse to detecting the swipe, device 1600 displays a full view ofrandom clock face generation affordance 1676 centered on screen 1680. Insome embodiments, as depicted by affordance 1676, a random clock facegeneration affordance may include a question mark (or other text and/orsymbol, such as the letter “R”) to convey to the user that, uponactivation of affordance 1676, device 1600 will generate a random clockface.

Note that screen 1680 also displays a partial view of previouslydisplayed clock face 1672. The partial view of 1672, along with updatedpaging affordance 1674 (updated to indicate that random clock facegeneration is the second available user interface in the sequence),helps orient the user to the sequence of clock faces and/or optionsavailable in the sequence. Further note that the partial view of randomclock face generation affordance 1676 on screen 1670 indicates to theuser that a swipe will center affordance 1676 on the display (e.g., asdisplayed on screen 1680) for user activation.

A user may activate affordance 1676, for example by contactingaffordance 1676 on the touch-sensitive display (e.g., touch 1682). Inresponse to detecting the contact, device 1600 displays screen 1690,which includes randomly generated clock face 1692 centered on thedisplay. As shown on screen 1690, new clock face 1692 includesaffordance 1694, which represents an affordance for launching astopwatch application, and affordance 1696, which displays the currenttemperature (e.g., obtained from a weather application).

In response to detecting an activation of affordance 1676, in someembodiments, the device remains in clock face selection mode aftercentering the displayed random clock face. In other embodiments, uponcentering the randomly generated clock face on the display, the deviceenters into clock face edit mode, as described above. This allows theuser to edit one or more aspects of the randomly generated clock face.In some embodiments, the device exits clock face selection mode andcenters the random clock face as a full-size clock face on the display.

It is to be appreciated that, while random clock face 1692 depicts arepresentation of an analog clock, any of the context-specific userinterfaces described herein (with any of the optional features describedherein) may be a random clock face generated in response to activatingthe random clock face generation affordance.

In some embodiments, the random clock face may be different from any ofthe other clock faces available in clock face selection mode. The devicemay accomplish this in multiple ways. In some embodiments, the devicemay randomly generate a random clock face, and then check the randomclock face against the other stored clock faces to ensure that it isdifferent. In other embodiments, the device may generate a random clockface and rely on the inherent probability that it will be different fromthe stored clock faces, given the sheer number of potential clock facesmade available by the techniques described herein.

In some embodiments, upon displaying the random clock face, the devicemay display a user prompt for generating a second random clock face.This allows the user to randomly generate another clock face if the userdoes not like the particular type of context-specific user interfaceand/or customized features of the random clock face. In someembodiments, the random clock face generation affordance may depict,e.g., a slot machine or other indication of a user prompt for generatinga second random clock face, to provide this feature.

In addition to centering a clock face on the display for selection, thedevice may also highlight the centered clock face in one or more ways.For example, in some embodiments, the centered clock face may bedisplayed by visibly distinguishing an outline around the centered clockface (e.g., by displaying a visible outline, or by distinguishing apre-existing outline already visible around the clock face), asillustrated by 1612, 1622, 1642, and 1672. In some embodiments, theoutline may be animated to depict a rhythmic expansion and contraction(e.g., animation similar to pulsing or breathing). In some embodiments,the centered clock face itself may be animated to depict a rhythmicexpansion and contraction. In some embodiments, the centered clock facemay be animated to depict flashing. In some embodiments, a color of thecentered clock face may be changed (e.g., a change in color and/orintensity). Any or all of these indications may be used to visuallyindicate that the centered clock face is currently selectable.

In some embodiments, the user may access clock face edit mode and clockface selection mode through a shared interface. For example, a contactwith a characteristic intensity above the intensity threshold may causethe device to enter clock face selection mode. In this example, screen1510 in FIG. 15 may represent clock face selection mode, with a pagingaffordance that indicates the currently selected clock face within asequence of selectable clock faces and/or clock face options. Uponentering clock face selection mode, in some embodiments, a secondcontact with a characteristic intensity above the intensity thresholdmay cause the device to enter into the clock face edit mode and selectthe currently centered clock face for editing. In other embodiments,upon entering clock face selection mode, the device may display anaffordance representing clock face edit mode. Upon detecting a contacton the displayed affordance, the device may enter into the clock faceedit mode and select the currently centered clock face for editing.These features help tie the context-specific user interface selectionand editing functionalities into a single interface that isuser-friendly and intuitive.

3. Additional Functionalities for Context-Specific User Interfaces

A user may wish for additional functionalities in a context-specificuser interface that may be applied to the user interfaces describedabove. For example, a user may wish to set reminders, launchapplications, and view the time at a designated location. Suchfunctionalities are not limited to particular user interfaces describedherein, but rather may be generally applied to any or all of them. Thefollowing functionalities are generalizable features that may beincorporated into any of the context-specific user interfaces describedherein. While a specific functionality may be described in reference toa particular context-specific user interface below, this is in no wayintended to be limiting.

FIG. 17A shows exemplary context-specific user interfaces that may beoperated on device 1700. Device 1700 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504) and a rotatable inputmechanism (e.g., 506 or 1540).

In this example, a user wants to set a reminder for 6:00 (this may be areminder for 6:00 at a specific day or a general reminder for 6:00 everyday). Device 1700 displays user interface screen 1702. Screen 1702depicts a clock face similar to those described in reference to FIGS.11A-C and includes affordance 1704, which indicates the time of day, anda sinusoidal wave indicating a path of the Sun through the day. Screen1702 further includes affordance 1708, which as described in FIG. 11Aindicates a current time of day by its position along the sinusoidalwave (10:09).

A user may contact the display, which then prompts the device to enterinto a user interaction mode. User interaction mode provides the useradditional interactions available within the user interface, such assetting a user reminder. Once in user interaction mode, a user moves therotatable input mechanism (e.g., movement 1708), and in response todetecting the movement, device 1700 displays screen 1710. Screen 1710displays a non-current time of day (6:00), as indicated by affordance1712 and the position of affordance 1714 along the sinusoidal wave. Theuser may use movement 1708 to scroll through times of day until adesignated time is displayed (in this case 6:00) so the user can set areminder for the designated time of day.

The user contacts the display at affordance 1714 (e.g., touch 1716), andin response to detecting the contact, device 1700 sets a reminder forthe indicated time of day (6:00). This allows the user to set adesignate a time of day for a user reminder.

FIG. 17B shows device 1700 at a later time of day (11:00). Device 1700displays screen 1720. Screen 1720 includes affordance 1722, whichindicates the current time, and affordance 1724, which indicates acurrent time of day by its position along the sinusoidal wave. As shownin FIG. 11B, in this context-specific user interface, a user may contactaffordance 1724 (e.g., touch 1726) to view user interface objectsrepresenting dawn, dusk, sunrise, and sunset.

In response to detecting the contact, device 1700 displays screen 1730.Screen 1730 includes affordance 1732, which indicates the current timeof day, and affordance 1734, which also indicates the current time ofday by its position along sinusoidal wave 1736. Line 1738 depicts theboundary between the daytime and nighttime portions of the display. Asdescribed above, screen 1730 includes user interface objects 1740(representing a time of dawn), 1742 (representing a time of sunrise),1744 (representing a time of sunset), and 1746 (representing a time ofdusk).

Importantly, screen 1730 also displays affordance 1748. Affordance 1748is a visual reminder of the time of day designated by the user (6:00) inFIG. 17A. Thus, the device now displays a user reminder for this time ofday, in this case in response to a user contact on affordance 1724.

In some embodiments, setting the user reminder may include displaying anaffordance representing a user prompt to set an alert for the designatedtime of day. This affordance may include a user interface for settingone or more properties of the alert.

In some embodiments, a user reminder may include a calendar event. Forexample, instead of a user setting the user reminder as described above,the device may import a calendar event from a calendar application.Using the example illustrated in FIG. 17B, affordance 1748 may representa calendar event imported from a calendar application. Importing acalendar event from a calendar application allows the user to track thetime of the calendar event compared with the current time and/or othertimes of interest (e.g., sunrise, sunset, dawn, or dusk). For example,the user may be able to view the time of a tennis match (stored as acalendar event) as part of screen 1730 and thereby gauge how much timeis left before the match is scheduled, or how much time is availablebetween the start of the match and sunset. In some embodiments, the usermay move the rotatable input mechanism (e.g., movement 1708), and inresponse to detecting the movement, the device may snap to the userreminder by visually distinguishing affordance 1748 and/or by updating adisplayed indication of time to indicate the time associated with theuser reminder represented by affordance 1748.

In some embodiments, the user reminder represents a recurring event. Insome embodiments, the time of the user reminder is based on a fixedchronological time. To use FIG. 17B as an example, if the user reminderis a tennis match, it may recur at the same chronological timethroughout the year, but the position of affordance 1748 relative toline 1738 may change throughout the year. This would allow the user todetermine whether sufficient daylight will be present throughout thematch on a given date simply by viewing the position of affordance 1748.In other embodiments, the time of the user reminder is based on a solarcondition (e.g., the amount of daylight or lack thereof). For example, auser reminder may reflect the time of a solar condition, such as aparticular time before sunset, or the time that the sun is at aparticular angle above the horizon. Therefore, if such a user reminderis recurring, the chronological time of the user reminder may vary overtime while still representing the same solar condition, allowing theuser to plan for viewing this solar condition at any time of the year.

The user reminder for the designated time of day may include one or moreoptional features. In some embodiments, the reminder may include avisual alert for the designated time of day. For example, the device maydisplay a visual alert on or before the designated time of day.Alternatively, the device may display at any time a visual affordancethat shows the designated time of day within the context of the currentuser interface. In the example of FIG. 17B, visual affordance 1748 isdisplayed along the sinusoidal wave to help the user understand how farthe designated time of day is from the current time of day.

In some embodiments, the user reminder may include an audio alert forthe designated time of day. For example, the device may play a sound onor before the designated time of day. In some embodiments, the userreminder may include a haptic alert generated on or before thedesignated time of day (e.g., using haptic feedback module 133 andtactile output generator 167). This haptic signal lets the user knowwhen the designated time of day is approaching.

Turning now to FIG. 18A, any or all of the context-specific userinterfaces described herein may include one or more complications. Onetype of complication a user may wish to use is a complication forlaunching an application. For example, the affordance representing thecomplication on the clock face may display a set of information from thecorresponding application. However, a user may wish to view additionalinformation from the application, or launch the full application itself.

FIG. 18A shows exemplary context-specific user interfaces that may beoperated on device 1800. Device 1800 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

Device 1800 displays user interface screen 1802. Screen 1802 includesclock face 1804 and affordances 1806 and 1808, which are displayed ascomplications. Affordances 1806 and 1808 represent applications andinclude a set of information obtained from the correspondingapplication. In this example, affordance 1806 represents a weatherapplication and displays weather conditions obtained from the weatherapplication. Affordance 1808 represents a calendar application anddisplays the current date obtained from the calendar application.Affordance 1806 and affordance 1808 are updated in accordance with datafrom the corresponding application. For example, affordance 1806 isupdated to display current weather conditions obtained from the weatherapplication. Affordance 1808 is updated to display the current dateobtained from the calendar application. For example, these complicationsmay be application widgets updated based on application data.

To launch the weather application, a user contacts the display ataffordance 1806 (e.g., touch 1810). In response, device 1800 launchesthe weather application, which is depicted on screen 1820. Screen 1820shows further weather information, including current weather conditions(e.g., user interface object 1822), an indication of the currentlocation (e.g., user interface object 1824), and an indication of thecurrent temperature (e.g., user interface object 1826).

FIG. 18B also depicts device 1800 displaying screen 1802. As depicted inFIG. 18A, screen 1802 includes clock face 1804 and affordances 1806 and1808, which are displayed as complications.

If a user wishes to launch the calendar application instead of theweather application, the user contacts the display at affordance 1808(e.g., touch 1812). In response, device 1800 launches the calendarapplication, which is depicted on screen 1830. Screen 1830 shows furthercalendar information, including user interface object 1832, whichdepicts the full date, and user interface object 1834, which representsa calendar event (in this case, a meeting at 1).

In some embodiments, a user interface screen may display a complicationthat represents an application and includes a set of informationobtained from the corresponding application. In some embodiments, asillustrated by FIGS. 18A and 18B, a user interface screen may display aplurality of complications that represent applications and include setsof information obtained from a plurality of applications, or a pluralityof sets of information obtained from a single application.

In some embodiments, as described above, a user may move a rotatableinput mechanism to scroll a displayed indication of time forward orbackward. In some embodiments, the device may display two or moreindications of time, and in response to detecting a movement of therotatable input mechanism, the device may update one or more of thedisplayed indications of time and keep another indication of timeconstant. To illustrate using screen 1802 in FIGS. 18A and B as anexample, if affordance 1808 represents an indication of current time(e.g., a digital display), the device may update the displayed clockface in response to detecting the movement of the rotatable inputmechanism while continuing to display the current time with affordance1808. The displayed clock face may be updated, for example, by animatinga clockwise or counter-clockwise movement of one or more clock hands,depending on whether the displayed time is scrolled forward or backward.

In some embodiments, the device may update other displayed complications(e.g., those that do not indicate a time per se) in response todetecting the movement of the rotatable input mechanism. For example, inaddition to updating the time displayed by clock face 1804, the devicemay also update the forecasted or historical weather condition displayedby affordance 1806 to correspond with the time indicated by clock face1804. In these embodiments, the device may forego updating anotherdisplayed complication in response to scrolling the displayed time. Forexample, a displayed stopwatch complication may remain the same whilethe displayed clock face is updated. In some embodiments, a displayedcomplication that is not updated in response to detecting the movementof the rotatable input mechanism may be visually distinguished, such asby changing a hue, saturation, and/or lightness of the displayedcomplication. This allows the user to distinguish which complicationsare updated and which remain constant.

Advantageously, these context-specific user interface methods, which maybe applied to any of the context-user interfaces described herein simplyby including an application complication, allow the user to view updatedinformation from a particular application while also presenting a quickway to launch the corresponding application in the same user interfaceobject. Moreover, the application and/or application informationdepicted by the complication may further be customized using the editingmethods described in reference to FIG. 15 (see, e.g., screen 1560 and1570).

A user may navigate screens on, e.g., a portable multifunction device,that include many affordances. These affordances may represent, forexample, applications that may be launched on the device. One suchaffordance may activate a context-specific user interface, such as thosedescribed herein. In order to help the user recognize that a particularaffordance corresponds to launching a context-specific user interface,an animation that visually connects the affordance to the interface maybe desirable.

FIG. 18C shows an exemplary user interface for editing a clock face thatcontains more than one complication, such as the ones depicted in FIGS.18A and 18B. FIG. 18C again depicts device 1800 displaying screen 1802,which includes clock face 1804, affordance 1806 representing a weatherapplication, and affordance 1808 representing a calendar application.

As discussed above in reference to FIG. 15, a user may customize thecomplications displayed on screen 1802 by entering clock face edit mode.The user contacts the touch-sensitive display of device 1800 with touch1814. Touch 1814 has a characteristic intensity above an intensitythreshold, which prompts device 1800 to enter a clock face edit mode,shown on screen 1840. Device 1800 indicates that the user has enteredclock face edit mode by visually distinguishing the clock face. In thisexample, screen 1840 shows a smaller version of the display of screen1802 (e.g., 1842), which includes a reduced size clock face, reducedsize complication 1844, which is based on complication 1806, and reducedsize complication 1846, which is based on complication 1808.

A user selects this clock face for editing by contacting displayed clockface 1842 (e.g., touch 1850). In some embodiments, touch 1850 is acontact on the touch-sensitive display. In some embodiments, touch 1850is a contact on the touch-sensitive display with a characteristicintensity above an intensity threshold. This causes device 1800 to enterinto clock face edit mode and display screen 1860. Screen 1860 displaysclock face 1862 for editing. Currently, affordance 1864 representing theweather application is selected for editing, as highlighted by outline1866. Also displayed is positional indicator 1868, which indicates theposition of the displayed complication in a series of complicationoptions using line 1870. Positional indicator 1868 further indicates tothe user that a rotatable input mechanism may be used to cycle throughoptions available for editing affordance 1864 (e.g., which set ofinformation from the weather application to display, or anotherapplication from which a set of information may be displayed). Pagingaffordance 1872 also displays the position of the aspect of clock face1862 currently selected for editing (i.e., complication 1864) in aseries of editable aspects.

Screen 1860 also displays affordance 1874, which represents the calendarapplication. To select this complication for editing, the user contactsdisplayed affordance 1874 (e.g., touch 1876). In response, device 1800displays screen 1880. Like screen 1860, screen 1880 displays clock face1862, affordance 1864 (which represents the weather application),positional indicator 1868, and affordance 1874 (which represents theweather application). Affordance 1874 is now highlighted for editing, asshown by outline 1882. The position of this complication option isdepicted by line 1884 in positional indicator 1868. Finally, pagingaffordance 1886 has been updated to display the position of affordancecomplication 1874 in a series of editable aspects of clock face 1862.The user may now edit the set of information displayed by affordance1874 using the rotatable input mechanism (e.g., which set of informationfrom the calendar application to display, or another application fromwhich a set of information may be displayed). In summary, while in clockface edit mode, a user may select a complication for editing when morethan one complication is displayed by contacting the displayedcomplication. In some embodiments, this causes the affordance to behighlighted (e.g., by a visible outline or other means for visiblydistinguishing the affordance described herein).

FIG. 19 shows exemplary context-specific user interfaces that may beoperated on device 1900. Device 1900 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

Device 1900 displays user interface screen 1902, which includes aplurality of affordances (e.g., affordances 1904 and 1906). Affordance1906 represents a clock face that includes an indication of time (e.g.,the hour hand, minute hand, and tick marks) and an outline (e.g., acircle or a polygon such as a square with rounded corners). In someembodiments, the clock face may indicate the current time. The usercontacts the touch-sensitive display (e.g., touch 1908) at affordance1906, and in response, device 1900 displays, sequentially, screens 1910,1920, and 1930 in continuous on-screen animation.

Screen 1910 shows outline 1912 being animated by progressivelydisplaying the element in a rotational motion (e.g., as if it is beingfilled in or drawn in a clockwise manner). Next, screen 1920 shows fulloutline 1922 and hour hand and minute hand 1924. Finally, screen 1930shows full outline 1932, hour hand and minute hand 1934, and hourindication 1936. Like the outline, the hour indications may also beprogressively filled in sequentially (e.g., in a clockwise manner).Importantly, at least one of the elements from affordance 1906 ismaintained on screen 1930 (e.g., an outline, or the hour and minutehands), but at a larger display size.

While FIG. 19 depicts an analog clock face with an hour hand and aminute hand, the techniques described in reference to FIG. 19 may applyto many context-specific user interfaces. For example, if the userinterface displays a representation of the Earth (as shown in FIG. 8),the affordance in the plurality of affordances may depict an Earth, andthe outline of the Earth may be retained and/or drawn in using aclockwise motion.

A user may also wish to receive an indication from a portablemultifunction device that a missed or unread notification is available.Thus, in any of the embodiments described herein, a device may receive anotification, determine whether the notification has been missed (e.g.,not viewed or marked as not read), and in accordance with adetermination that the notification has been missed, display anaffordance indicating a missed notification. in accordance with adetermination that the notification has not been missed, the device mayforego displaying the affordance indicating a missed notification. Insome embodiments, an aspect of the displayed affordance represents anumber of missed notifications received by the electronic device. Forexample, the displayed affordance may change color, change size, or beanimated (e.g., to depict pulsing) to represent a number of missednotifications. In some embodiments, in response to receiving datarepresenting user viewing of the missed notification, the device mayremove the displayed affordance. This provides the user a quick visualreminder that a notification may be viewed.

A user may also wish to launch an application, such as a stopwatchapplication, from any of the context-specific user interfaces describedherein. Thus, in any of the embodiments described herein, a device maydisplay a stopwatch progress affordance that indicates a currentlyrunning stopwatch application. For example, the stopwatch progressaffordance may depict a representation of a digital stopwatch (e.g.,similar to affordance 1694 in FIG. 16C). This representation may becontinuously updated to indicate a stopwatch time generated by thecurrently running stopwatch application. A user may contact thestopwatch progress affordance, and in response to detecting the contact,the device may launch the stopwatch application. This provides afunctional reminder that a stopwatch is currently running from anycontext-specific user interface.

When traveling, a user may wish to quickly access the time at home, oranother designated location. Thus, in any of the embodiments describedherein, a device may include a location sensor (e.g., GPS sensor 532and/or GPS module 135). While any clock face is displayed on thedisplay, a user may contact the display, and in response to detectingthe contact, the device may access a designated home location (e.g., ahome time zone). The device may obtain a current time zone (i.e., at thecurrent location of the device), determine whether the current time zoneis different from the home time zone, and in accordance with adetermination that the current time zone is different from the home timezone, update the displayed clock face to indicate current time at thehome time zone. In accordance with a determination that the current timezone is not different from the home time zone, the device may continueto display the same clock face to indicate current time at both the hometime zone and the current time zone.

In some embodiments, a user may designate the home time zone. Forexample, the device may provide a user interface for designating thehome time zone.

In other embodiments, the device may designate the home time zone. Forexample, the device could base this designation on data representingamount of time spent at a location, which times of day are spent at thelocation, and/or a number of contact entries associated with thelocation. In this way, the device may automatically be able to designatea home time zone.

A user may wish to display different context-specific user interfaces,such as those described herein, depending on a particular context. Forexample, a user may wish to display a specific context-specific userinterface or specific content (e.g., information provided by a displayedcomplication) while at work, then display a different context-specificuser interface or different content while at home. In some embodiments,a user may designate a time of day to change the displayedcontext-specific user interface. In some embodiments, a user maydesignate an interval during the day wherein a particularcontext-specific user interface is displayed. In other embodiments, thedevice may include a location sensor, and a user may designate acontext-specific user interface to be displayed at a particular location(e.g., a home or office). In some embodiments, the device may employ aheuristic method to track previous user interactions, such as a time ofday and/or location whereupon a user has changed context-specific userinterfaces, a particular context-specific user interface that has beenselected or de-selected, and the like. For example, if a user haschanged context-specific user interfaces at an approximately regulartime after returning home from work, the device may display a promptasking if the user would like to change context-specific user interfacesat the same time on the following day. In some embodiments, the deviceautomatically changes the context-specific user interface based on aprevious user interaction. In other embodiments, the device prompts theuser to change the context-specific user interface based on a previoususer interaction.

It may be desirable to vary the display of any of the devices describedherein. Thus, in any of the embodiments described herein, a device maydisplay a clock face that includes a plurality of pixels, detect amovement of the device (as described above), and in response todetecting the movement, move the displayed clock face on the display.Moving may include modifying a subset of the pixels in the plurality(e.g., by changing color and/or intensity of one or more pixels).

A user may wish to use a virtual tachymeter (e.g., a tachymeter that isnot based on a physical tachymeter dial built onto the device) on any ofthe devices described herein. A virtual tachymeter may be provided, forexample, by a tachymeter user interface object that may be displayed ona dedicated tachymeter user interface screen, or on any of the userinterface screens described herein (e.g., as a tachymeter complication).The user may provide a user input to start the virtual tachymeter and,subsequently the user may stop the virtual tachymeter by providing asecond user input. For example, the tachymeter user interface object mayinclude a start affordance, a stop affordance, or a combined start/stopaffordance. The user may start the virtual tachymeter by contacting thestart affordance or the start/stop affordance and stop the virtualtachymeter by contacting the stop affordance or the start/stopaffordance. In another example, one or both user inputs may be an inputon a mechanical button (e.g., a rotation and/or depression of therotatable and depressible input mechanism 506, and/or a press on button508) to start and/or stop the virtual tachymeter. In some embodiments,one or both user inputs may be an audio (e.g., verbal) input.

After the user has stopped the virtual tachymeter, the device maydisplay a time value based on the time elapsed between start and stop.This time value may be based on, for example, a number of units of timein a predetermined interval (e.g., the number of seconds in an hour). Insome embodiments, the displayed time value may be based on the number ofunits of time in the predetermined interval (e.g., the number of secondsin an hour) divided by the time elapsed between start and stop. In someembodiments, the user may customize the units of time used by thetachymeter, the units of time in the predetermined interval, and/or thepredetermined interval. In some embodiments, while the virtualtachymeter is running, the tachymeter user interface object may includean updating display to indicate the passage of time, such as a runningor continuously updated countdown of the time value, a rotating shape,and the like. Advantageously, since the tachymeter is virtual, it maymeasure any increment or interval of time because it is not constrainedor fixed like a traditional tachymeter, such as a watch tachymeter. Forexample, a watch tachymeter is typically limited to measuring times lessthan or equal to 60 seconds, because the displayed time values are fixed(e.g., painted or etched onto a tachymeter dial) and only apply tovalues within one full rotation of the second hand.

A user may wish to use a virtual telemeter (e.g., a telemeter that isnot based on a physical telemeter dial built onto the device) on any ofthe devices described herein. A virtual telemeter may be provided, forexample, by a telemeter user interface object that may be displayed on adedicated telemeter user interface screen, or on any of the userinterface screens described herein (e.g., as a telemeter complication).

The user may provide a user input to start the virtual telemeter and,subsequently the user may stop the virtual telemeter by providing asecond user input. For example, the telemeter user interface object mayinclude a start affordance, a stop affordance, or a combined start/stopaffordance. The user may start the virtual telemeter by contacting thestart affordance or the start/stop affordance and stop the virtualtelemeter by contacting the stop affordance or the start/stopaffordance. In another example, one or both user inputs may be an inputon a mechanical button (e.g., a rotation and/or depression of therotatable and depressible input mechanism 506, and/or a press on button508) to start and/or stop the virtual telemeter. In some embodiments,one or both user inputs may be an audio (e.g., verbal) input. After theuser has stopped the virtual telemeter, the device may display adistance based on the time elapsed between start and stop. This distancemay be based on the speed of sound. For example, the user may seelightning, start the telemeter, and stop the telemeter when the userhears thunder. In this case, the distance reported by the telemeter willindicate the distance between the user and the lightning, based on thetime interval between when the light reaches the user and when the soundreaches the user. In some embodiments, the user may designate the unitsfor reporting the distance (e.g., kilometers, miles, etc.). In someembodiments, while the virtual telemeter is running, the telemeter userinterface object may include an updating display to indicate the passageof time, such as a running or continuously updated distance, a rotatingshape, and the like. Advantageously, since the telemeter is virtual, itmay measure any increment or interval of time because it is notconstrained or fixed like a traditional telemeter, such as a watchtelemeter. For example, a watch telemeter is typically limited tomeasuring times less than or equal to 60 seconds, because the displayedtime values are fixed (e.g., painted or etched onto a telemeter dial)and only apply to values within one full rotation of the second hand.

A user may wish to use a repeated interval timer on any of the devicesdescribed herein, e.g., a timer that provides a user alert that isrepeated at a certain interval. For example, if the user is exercising(e.g., interval training), they may wish to receive an alert every 30seconds to change their mode of exercise or take a break. In anotherexample, a user taking medication may wish to receive an alert to taketheir medication every hour, 4 hours, 6 hours, 12 hours, 24 hours, andso forth. Any suitable interval or duration of time may be used. In someembodiments, the device may display a repeated interval timer userinterface. The repeated interval timer user interface may include, forexample, an affordance for the user to designate the interval, thetimescale for the interval (e.g., seconds, minutes, hours, days, weeks,months, years, etc.), and the like. In response to receiving datarepresenting a user-designated time interval, the device may provide auser alert that is repeated at times based on the user-designated timeinterval. In some embodiments, the alert may include a visual alert, anaudio alert, and/or a haptic alert (e.g., using haptic feedback module133 and tactile output generator 167), or any combination thereof.Rather than being based on a designated end point (e.g., a reminder fora particular day or time), the repeated interval timer is based onproviding the user a demarcation of a particular interval of time. Insome embodiments, the repeated interval timer runs until the user endsthe timer. In some embodiments, the device may further display anaffordance for ending the repeated interval timer (e.g., as part of therepeated interval timer user interface, or at the time of the useralert).

In some embodiments, any of the devices described herein may furthergenerate or receive a user alert including information and display auser notification based on the alert on any of the user interfacescreens described herein. The user notification may be, for example, anotification banner displayed across a portion of the display. Thenotification banner may include a portion of the information of thealert. An example of a user alert may include without limitation adetermination that the user has crossed the boundary of a time zone. Insome embodiments, the device has a location sensor (e.g., GPS sensor 532and/or GPS module 135), and the device obtains a current location of thedevice from the location sensor. Using the location sensor, the devicemay determine whether the current location of the device is in adifferent time zone, as compared to a previous location of the device,for example the location of the device at the time of a previous userinteraction (e.g., the last time the user looked at the display, or thelast time the device detected a user movement of the device, such as awrist raise). In accordance with the determination that the currentlocation is in a different time zone than the previous location, thedevice may display a notification banner across a portion of thedisplay. In some embodiments, the notification banner may include analert indicating that the user has crossed a time zone, a notificationof the current time in the new time zone, and so forth. In someembodiments, the device may prompt the user whether to accept the timechange (e.g., the device may display an affordance for accepting thetime change and/or an affordance for rejecting the time change). Theuser prompt may be displayed as part of the notification banner, or theuser prompt may be displayed in response to detecting a user contact onthe displayed notification banner. In response to receiving dataindicating a user acceptance of the time change (e.g., a contact on thedisplayed affordance for accepting the time change), the device mayupdate the displayed time based on the new time zone. In response toreceiving data indicating a user rejection of the time change (e.g., acontact on the displayed affordance for rejecting the time change), thedevice may forego updating the displayed time based on the new timezone.

FIG. 20 is a flow diagram illustrating process 2000 for providingcontext-specific user interfaces. In some embodiments, process 2000 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 600 (FIGS.6A and 6B). Some operations in process 2000 may be combined, the orderof some operations may be changed, and some operations may be omitted.Process 2000 provides context-specific user interfaces that give theuser an immediate indication of elapsed time before viewing, makingthese interfaces less confusing and, thus, conserving power andincreasing battery life.

At block 2002, the device receives data representing a user input (e.g.,602). At block 2004, responsive at least in part to receiving the data,the device displays a user interface screen including a clock face(e.g., 606) indicating a first time (the first time precedes a currenttime). At block 2006, the device updates the user interface screen byanimating the clock face to transition from indicating the first time toindicating the current time (animation represents the passage of timefrom the first time to the current time; see, e.g., 612).

Note that details of the processes described above with respect toprocess 2000 (FIG. 20) are also applicable in an analogous manner to themethods described below. For example, process 2100 (FIG. 21), process2200 (FIG. 22), process 2300 (FIG. 23), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2000. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 20 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2000 may be relevant to process 2100(FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 21 is a flow diagram illustrating process 2100 for providingcontext-specific user interfaces. In some embodiments, process 2100 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 700 (FIGS.7A and 7B). Some operations in process 2100 may be combined, the orderof some operations may be changed, and some operations may be omitted.Process 2100 provides context-specific user interfaces that combine astopwatch function and a timekeeping function, making these interfacesat once multifunctional and less confusing to the user, thus conservingpower and increasing battery life.

At block 2102, the device displays a clock face that indicates currenttime and includes a user interface object with an hour hand and a minutehand, one or more indications of an hourly timescale, and a stopwatchhand (e.g., as on screen 702). At block 2104, the device receives datarepresenting a user input (e.g., touch 712). At block 2106, responsiveat least in part to receiving the data, the device substitutes the oneor more indications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand (e.g., 724). At block 2108, the deviceanimates the stopwatch hand to reflect passage of time (e.g., cf. 726and 736).

Note that details of the processes described above with respect toprocess 2100 (FIG. 21) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2200 (FIG. 22), process 2300 (FIG. 23), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2100. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 21 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2100 may be relevant to process 2000(FIG. 20), process 2200 (FIG. 22), process 2300 (FIG. 23), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 22 is a flow diagram illustrating process 2200 for providingcontext-specific user interfaces. In some embodiments, process 2200 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5), 800 (FIG. 8),900 (FIG. 9), or 1000 (FIG. 10). Some operations in process 2200 may becombined, the order of some operations may be changed, and someoperations may be omitted. Process 2200 provides context-specific userinterfaces that provide timekeeping and geographical/astronomicalinformation, making these interfaces at once multifunctional and lessconfusing to the user, thus conserving power and increasing batterylife.

At block 2202, the device displays a user interface screen that includesa first affordance representing a simulation of a first region of theEarth as illuminated by the Sun at current time (e.g., 804) and a secondaffordance that indicates the current time (e.g., 806). At block 2204,the device receives data representing a user input (e.g., swipe 812). Atblock 2206, responsive at least in part to receiving the data, thedevice rotates the simulation of the Earth to display a second region ofthe Earth as illuminated by the Sun at the current time (e.g., 822).Optionally, at block 2206, the device displays a third affordancerepresenting a moon (e.g., 808, 826, 846, 1016, and 1034), detects acontact on the displayed third affordance, and responsive at least inpart to detecting the contact, updates the user interface screen bydisplaying a fourth affordance representing a simulation of the Moon asseen from the Earth at the current time (e.g., 904) and a fifthaffordance that indicates the current time (e.g., 906). Optionally, atblock 2206, the device displays a sixth affordance representing a solarsystem (e.g., 810, 828, and 848), detects a contact on the displayedsixth affordance, and responsive at least in part to detecting thecontact, updates the user interface screen by displaying a seventhaffordance including representations of the Sun, the Earth, and one ormore non-Earth planets at their respective positions at a current time(e.g., 1004) and an eighth affordance that indicates the current time(e.g., 1012).

Note that details of the processes described above with respect toprocess 2200 (FIG. 22) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2300 (FIG. 23), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2200. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 22 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2200 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2300 (FIG. 23), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 23 is a flow diagram illustrating process 2300 for providingcontext-specific user interfaces. In some embodiments, process 2300 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1100 (FIGS.11A-C). Some operations in process 2300 may be combined, the order ofsome operations may be changed, and some operations may be omitted.Process 2300 provides context-specific user interfaces that allow theuser to view current time of day with respect to daylight/nighttimeconditions, making these interfaces at once multifunctional and lessconfusing to the user, thus conserving power and increasing batterylife.

At block 2302, the device displays a user interface screen that includesa first portion indicating daytime (e.g., 1104); a second portionindicating nighttime (e.g., 1106); a user interface object representinga sinusoidal wave with a period representing a day (e.g., 1108); a firstaffordance representing the Sun displayed at a first position on thesinusoidal wave indicating a current time of the day and whether thecurrent time of the day is during daytime or nighttime (e.g., 1110); anda second affordance, the second affordance indicating the current timeof day (e.g., 1114). Optionally, at block 2304, the device receives acontact on the touch-sensitive display at the first affordance at thefirst position indicating the current time (e.g., 1148). Optionally, atblock 2306, while continuing to receive the user contact, the devicedetects movement of the user contact from the first position to a secondposition on the displayed sinusoidal wave without a break in contact ofthe user contact on the touch-sensitive display (second position on thesinusoidal wave indicates a non-current time; see, e.g., touch 1166).Optionally, at block 2308, responsive at least in part to detecting thecontact at the second position, the device translates the firstaffordance on-screen from the first position on the sinusoidal wave tothe second position on the sinusoidal wave (translation tracks thedisplayed sinusoidal wave; see, e.g., 1162). Optionally, at block 2310,the device updates the second affordance to indicate the non-currenttime (e.g., 1168).

Note that details of the processes described above with respect toprocess 2300 (FIG. 23) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2300. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 23 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2300 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 24 is a flow diagram illustrating process 2400 for providingcontext-specific user interfaces. In some embodiments, process 2400 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1200 (FIG.12). Some operations in process 2400 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process2400 provides context-specific user interfaces that provide an easilydistinguishable background image and indications of date and/or timecreated out of the background, making these interfaces easier for theuser to view, thus conserving power and increasing battery life.

At block 2402, the device displays a user interface screen that includesa background, based on an image (e.g., 1204 and 1212), with a pluralityof pixels (a subset of the pixels are modified in appearance relative tothe image such that the subset of pixels represents one or more of afirst user interface object indicating a date and a second userinterface object indicating a time of day; see, e.g., 1206 and/or 1208).Optionally, at block 2402, one of the first user interface object andthe second user interface object is a color independent of thebackground. Optionally, at block 2404, if one of the first userinterface object and the second user interface object is a colorindependent of the background, the device receives data representing abackground color of the background at a position of the displayed firstuser interface object or the displayed second user interface object(first color is different from background color at the position of thedisplayed first user interface object or the displayed second userinterface object).

Note that details of the processes described above with respect toprocess 2400 (FIG. 24) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2400. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 24 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2400 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 25 is a flow diagram illustrating process 2500 for providingcontext-specific user interfaces. In some embodiments, process 2500 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1200 (FIG.12). Some operations in process 2500 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process2500 provides context-specific user interfaces that provide an easilydistinguishable background image and indications of date and/or timecreated out of the background, making these interfaces easier for theuser to view, thus conserving power and increasing battery life.

At block 2502, the device accesses a folder with two or more images. Atblock 2504, the device selects a first image from the folder. At block2506, the device displays a user interface screen (e.g., 1202) thatincludes a background based on the first image, the backgroundcontaining a plurality of pixels (a subset of the pixels are modified inappearance relative to the image such that the subset of pixelsrepresents one or more of a first user interface object indicating adate and second user interface object indicating a time of day; see,e.g., 1204). Optionally, at block 2508, after displaying the first userinterface screen, the device receives first data representing a userinput. Optionally, at block 2510, responsive at least in part toreceiving the first data, the device receives second data representingthe displayed first background. Optionally, at block 2512, the deviceselects a second image from the folder (second image is different fromthe first image; see, e.g., 1212). Optionally, at block 2514, the devicedisplays a second user interface screen (e.g., 1210) that includes abackground based on the first image, the background containing aplurality of pixels (a subset of the pixels are modified in appearancerelative to the image such that the subset of pixels represents one ormore of a first user interface object indicating a date and second userinterface object indicating a time of day.

Note that details of the processes described above with respect toprocess 2500 (FIG. 25) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2500. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 25 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2500 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 26 is a flow diagram illustrating process 2600 for providingcontext-specific user interfaces. In some embodiments, process 2600 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1300 (FIGS.13A and 13B). Some operations in process 2600 may be combined, the orderof some operations may be changed, and some operations may be omitted.Process 2600 provides context-specific user interfaces that providetimekeeping and a variable animated sequence, making these interfacesmore interactive and engaging to the user, thus improving the interfacewhile conserving power and increasing battery life.

At block 2602, the device detects a user input at a first time (e.g.,1304). At block 2604, responsive at least in part to detecting the userinput, the device displays a user interface screen including a firstuser interface object indicating the first time (e.g., 1306) and asecond user interface object (e.g., 1308). At block 2606, the deviceanimates the second user interface object with a sequential display of afirst animated sequence, a second animated sequence after the firstanimated sequence, and a third animated sequence after the secondanimated sequence (first animated sequence, second animated sequence,and third animated sequences are different; see, e.g., screens 1302,1310, and 1320). At block 2608, the device detects a second user inputat a second time of day (e.g., 1332). At block 2610, responsive at leastin part to detecting the second user input, the device accesses datarepresenting the previously displayed second animated sequence. At block2612, the device selects a fourth animated sequence different from thefirst animated sequence and the second animated sequence. At block 2614,the device displays a second user interface screen including the firstuser interface object (first user interface object indicates second timeof day; see, e.g., 1334) and a third user interface object related tothe second user interface object (e.g., 1336). At block 2616, the deviceanimates the third user interface object with a sequential display ofthe first animated sequence, the fourth animated sequence after thefirst animated sequence, and the third animated sequence after thefourth animated sequence (see, e.g., screens 1330, 1340, and 1350).

Note that details of the processes described above with respect toprocess 2600 (FIG. 26) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2600. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 26 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2600 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27A is a flow diagram illustrating process 2700 for providingcontext-specific user interfaces. In some embodiments, process 2700 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1400 (FIG.14A). Some operations in process 2700 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process2700 provides context-specific user interfaces that are less confusingto the user, thus conserving power and increasing battery life.

At block 2702, the device detects a user movement of the device (e.g.,1404). At block 2704, responsive at least in part to detecting themovement, the device displays an animated reveal of a clock face bydisplaying an hour hand and a minute hand (e.g., 1424), displaying afirst hour indication (e.g., 1436), and displaying a second hourindication after the first (second hour indication is after the firsthour indication on clock face in clockwise direction; see, e.g., 1438).

Note that details of the processes described above with respect toprocess 2700 (FIG. 27A) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG.27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2700. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27A have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2700 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27B is a flow diagram illustrating process 2710 for indicating timeusing a character-based user interface. In some embodiments, process2710 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2710may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2710 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2712, a character user interface object that indicates a firsttime is displayed. The character user interface object includesrepresentations of a first limb and a second limb and indicates a firsttime by indicating a first hour with the first limb and a first minutewith the second limb. At block 2714, the character user interface objectis updated to indicate a second time by indicating a second hour withthe first limb and a second minute with the second limb. Optionally, atblock 2714, updating the character user interface object to indicate asecond time includes an extension of the first limb and a retraction ofthe second limb.

Note that details of the processes described above with respect toprocess 2710 (FIG. 27B) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2720 (FIG. 27C), process 2730 (FIG.27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2710. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27B have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2710 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27C is a flow diagram illustrating process 2720 for indicating timeusing a character-based user interface. In some embodiments, process2720 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2720may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2720 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2722, a character user interface object that indicates a firsttime value is displayed. The character user interface object includes arepresentation of a first limb with a first endpoint and a secondendpoint. The first endpoint is an axis of rotation for the limb, andthe second endpoint indicates a first time value. At block 2724, thecharacter user interface object is updated to indicate a second timevalue. Updating the character user interface object includes moving thefirst endpoint and moving the second endpoint to indicate the secondtime value.

Note that details of the processes described above with respect toprocess 2720 (FIG. 27C) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2730 (FIG.27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2720. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27C have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2720 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27D is a flow diagram illustrating process 2730 for indicating timeusing a character-based user interface. In some embodiments, process2730 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2730may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2730 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2732, a character user interface object that indicates a firsttime value is displayed. The character user interface object includes arepresentation of a first limb with a first segment and a secondsegment. The first segment of the limb connects a first endpoint to ajoint. The second segment connects a second endpoint to the joint. Thejoint is an axis of rotation for the second segment. The position of thesecond endpoint indicates a first time value. At block 2734, thecharacter user interface object is updated to indicate a second timevalue. Updating the character user interface object includes moving thesecond endpoint along the axis of rotation to indicate the second timevalue.

Note that details of the processes described above with respect toprocess 2730 (FIG. 27D) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2730. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27D have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2800 (FIG. 28), process 2900 (FIG. 29), process3000 (FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), andprocess 3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 2730 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2740 (FIG. 27E), process 2750(FIG. 27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000(FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 27E is a flow diagram illustrating process 2740 for indicating timeusing a character-based user interface. In some embodiments, process2740 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2740may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2740 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2742, a character user interface object that indicates time isdisplayed. At block 2744, first data indicative of an event is received.At block 2746, a determination is made as to whether the event meets acondition. At block 2748, in accordance with the determination that theevent meets the condition, the character user interface object isupdated by changing a visual aspect of the character user interfaceobject.

Note that details of the processes described above with respect toprocess 2740 (FIG. 27E) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2730 (FIG. 27D), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2740. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27E have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2740 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2720 (FIG. 27C), process 2730 (FIG. 27D), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27F is a flow diagram illustrating process 2750 for indicating timeusing a character-based user interface. In some embodiments, process2750 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2750may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2750 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2752, the display is set to an inactive state. At block 2754,first data indicative of an event is received. At block 2756, inresponse to receiving the first data, the display is set to an activestate. At block 2758, a character user interface object is displayed ona side of the display. At block 2760, the character user interfaceobject is animated towards a center of the display. At block 2762, thecharacter user interface object is displayed at the center of thedisplay in a position that indicates a current time.

Note that details of the processes described above with respect toprocess 2750 (FIG. 27F) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2750. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27F have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2750 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 28 is a flow diagram illustrating process 2800 for providingcontext-specific user interfaces. In some embodiments, process 2800 maybe performed at an electronic device with a touch-sensitive displayconfigured to detect intensity of contacts, such as 500 (FIG. 5) or 1500(FIG. 15). Some operations in process 2800 may be combined, the order ofsome operations may be changed, and some operations may be omitted.Process 2800 provides for editing multiple aspects of variouscontext-specific user interfaces in a comprehensive yet easy-to-usemanner, thus conserving power and increasing battery life.

At block 2802, the device displays a user interface screen that includesa clock face (e.g., 1504). At block 2804, the device detects a contacton the display (contact has characteristic intensity; see, e.g., touch1508). At block 2806, a determination is made as to whether thecharacteristic intensity is above an intensity threshold. At block 2808,in accordance with a determination that the characteristic intensity isabove the intensity threshold, the device enters a clock face edit mode(see, e.g., screen 1510). In accordance with a determination that thecharacteristic intensity is not above the intensity threshold (where theclock face includes an affordance representing an application, and wherethe contact is on the affordance representing the application), thedevice may launch the application represented by the affordance. Atblock 2810, the device visually distinguishes the displayed clock faceto indicate edit mode (e.g., 1512). At block 2812, the device detects asecond contact on the display at the visually distinguished clock face(e.g., 1520). At block 2814, responsive at least in part to detectingthe second contact, the device visually indicates an element of theclock face for editing (e.g., 1534).

Note that details of the processes described above with respect toprocess 2800 (FIG. 28) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2800. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 28 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2900 (FIG. 29), process 3000(FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 2800 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2900 (FIG. 29), process3000 (FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 29 is a flow diagram illustrating process 2900 for providingcontext-specific user interfaces. In some embodiments, process 2900 maybe performed at an electronic device with a touch-sensitive displayconfigured to detect intensity of contacts, such as 500 (FIG. 5) or 1600(FIGS. 16A-C). Some operations in process 2900 may be combined, theorder of some operations may be changed, and some operations may beomitted. Process 2900 provides for selecting context-specific userinterfaces in a comprehensive yet easy-to-use manner, thus conservingpower and increasing battery life.

At block 2902, the device displays a user interface screen that includesa clock face (e.g., 1604). At block 2904, the device detects a contacton the display (contact has characteristic intensity (e.g., 1606). Atblock 2906, a determination is made as to whether the characteristicintensity is above an intensity threshold. At block 2908, in accordancewith a determination that the characteristic intensity is above theintensity threshold, the device enters a clock face selection mode (see,e.g., screen 1610). In accordance with a determination that thecharacteristic intensity is not above the intensity threshold (where theclock face includes an affordance representing an application, and wherethe contact is on the affordance representing the application), thedevice may launch the application represented by the affordance. Atblock 2910, the device visually distinguishes the displayed clock faceto indicate selection mode (the clock face is centered on the display;see, e.g., 1612). At block 2912, the device detects a swipe on thedisplay at the visually distinguished clock face (e.g., 1618). At block2914, responsive at least in part to detecting the swipe, the devicecenters a second clock face on the display (e.g., 1616 on screen 1620).

Note that details of the processes described above with respect toprocess 2900 (FIG. 29) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2900. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 29 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 3000(FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 2900 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process3000 (FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 30 is a flow diagram illustrating process 3000 for providingcontext-specific user interfaces. In some embodiments, process 3000 maybe performed at an electronic device with a touch-sensitive displayconfigured to detect intensity of contacts, such as 500 (FIG. 5), 1500(FIG. 15), or 1600 (FIGS. 16A-C). Some operations in process 3000 may becombined, the order of some operations may be changed, and someoperations may be omitted. For example, FIG. 30 illustrates an exemplaryembodiment for accessing clock face selection and edit modes from asingle interface, but other orders of operation are possible. Process3000 provides for selecting and editing context-specific user interfacesin a comprehensive yet easy-to-use manner, thus conserving power andincreasing battery life.

At block 3002, the device displays a user interface screen that includesa clock face (e.g., 1502 and/or 1602). At block 3004, the device detectsa contact on the display (contact has characteristic intensity; see,e.g., 1508 and/or 1606). At block 3006, a determination is made as towhether the characteristic intensity is above an intensity threshold. Atblock 3008, in accordance with a determination that the characteristicintensity is above the intensity threshold, the device enters a clockface selection mode and visually distinguishes the displayed clock faceto indicate selection mode (the clock face is centered on the display;see, e.g., 1512 and/or 1612). In accordance with a determination thatthe characteristic intensity is not above the intensity threshold (wherethe clock face includes an affordance representing an application, andwhere the contact is on the affordance representing the application),the device may launch the application represented by the affordance. Atblock 3010, the device detects a swipe on the display at the visuallydistinguished clock face (e.g., 1618). At block 3012, responsive atleast in part to detecting the swipe, the device centers a second clockface on the display (e.g., 1616 on screen 1620). At block 3014, thedevice detects a contact on the touch-sensitive display at the displayedsecond clock face (e.g., 1520). At block 3016, responsive at least inpart to detecting the contact, the device enters a clock face edit modefor editing the second clock face (see, e.g., screen 1530).

Note that details of the processes described above with respect toprocess 3000 (FIG. 30) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 3000. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 30 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For example, the device coulddetect a contact on the displayed first clock face before detecting theswipe. In this case, the device may enter clock face edit mode to editthe first clock face. For brevity, all of these details are not repeatedhere. Additionally, it should be noted that aspects of process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E),process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900 (FIG. 29),process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300 (FIG.33) may be incorporated with one another. Thus, the techniques describedwith respect to process 2900 may be relevant to process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750(FIG. 27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33).

FIG. 31 is a flow diagram illustrating process 3100 for providingcontext-specific user interfaces. In some embodiments, process 3100 maybe performed at an electronic device with a touch-sensitive display anda rotatable input mechanism, such as 500 (FIG. 5) or 1600 (FIGS. 17A and17B). Some operations in process 3100 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process3100 provides for setting a user reminder in various context-specificuser interfaces in a less confusing and easy-to-access manner, thusconserving power and increasing battery life.

At block 3102, the device displays a user interface screen that includesa clock face (e.g., screen 1702) and an affordance on the clock face(affordance indicates first time of day; see, e.g., 1706). At block3104, the device detects a contact on the display. At block 3106,responsive at least in part to detecting the contact, the device entersa user interaction mode. At block 3108, while in user interaction mode,the device detects a movement of the rotatable input mechanism (e.g.,1708). At block 3110, responsive at least in part to detecting themovement, the device updates the affordance to indicate a second time ofday (e.g., 1714). At block 3112, the device detects a second contact atthe affordance (e.g., 1716). At block 3114, responsive at least in partto detecting the contact, the device sets a user reminder for the secondtime of day (e.g., 1748).

Note that details of the processes described above with respect toprocess 3100 (FIG. 31) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 3100. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 31 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900(FIG. 29), process 3000 (FIG. 30), process 3200 (FIG. 32), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 3100 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process2900 (FIG. 29), process 3000 (FIG. 30), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 32 is a flow diagram illustrating process 3200 for providingcontext-specific user interfaces. In some embodiments, process 3200 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1800 (FIGS.18A-18C). Some operations in process 3200 may be combined, the order ofsome operations may be changed, and some operations may be omitted.Process 3200 provides for launching an application directly from anapplication complication (which also provides application information)through various context-specific user interfaces, thus conserving powerand increasing battery life by easily linking various user applicationsand a timekeeping clock face.

At block 3202, the device displays a user interface screen that includesa clock face (e.g., 1804) and an affordance (affordance represents anapplication and displays a set of information from the application) as acomplication (e.g., 1806 and/or 1808). At block 3204, the device detectsa contact on the affordance (e.g., 1810 and/or 1812). At block 3206,responsive at least in part to detecting the contact, the devicelaunches the application represented by the affordance (see, e.g.,screen 1820 and/or 1830).

Note that details of the processes described above with respect toprocess 3200 (FIG. 32) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 3100. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 32 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900(FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 3200 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and/orprocess 3300 (FIG. 33).

FIG. 33 is a flow diagram illustrating process 3300 for providingcontext-specific user interfaces. In some embodiments, process 3300 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1900 (FIG.19). Some operations in process 3300 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process3300 provides a simple means by which to access various context-specificuser interfaces, thus conserving power and increasing battery life.

At block 3302, the device displays a user interface screen that includesa plurality of affordances (a first affordance in the pluralityindicates a clock face, which includes an indication of time and anoutline; see, e.g., screen 1902 and affordance 1906). At block 3304, thedevice detects a contact on first affordance (e.g., 1908). At block3306, responsive at least in part to detecting the contact, the devicesubstitutes the display of user interface screen with a second userinterface screen (substitution includes retaining the indication of timeor the outline at a larger size; see, e.g., screen 1930 with outline1932 and/or hour hand and minute hand 1934).

Note that details of the processes described above with respect toprocess 3300 (FIG. 33) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), and/or process 3200 (FIG. 32) may includeone or more of the characteristics of the various methods describedabove with reference to process 3300. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 33 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900(FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and process3200 (FIG. 32) may be incorporated with one another. Thus, thetechniques described with respect to process 3300 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and/orprocess 3200 (FIG. 32).

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A, 1B, 3, 5A, and 5B) are all included within thescope of the techniques described herein.

FIG. 34 shows exemplary functional blocks of an electronic device 3400that, in some embodiments, performs the features described above. Asshown in FIG. 34, an electronic device 3400 includes a display unit 3402configured to display graphical objects; a touch-sensitive surface unit3404 configured to receive user gestures; one or more RF units 3406configured to detect and communicate with external electronic devices;and a processing unit 3408 coupled to display unit 3402, touch-sensitivesurface unit 3404, and RF unit(s) 3406. In some embodiments, processingunit 3408 is configured to support an operating system 3410 and anapplications unit 3412. In some embodiments, operating system 3410 isconfigured to launch applications with applications unit 3412 or enter adevice mode. In some embodiments, operating system 3410 is configured tolaunch an application, enter a clock face edit mode of the electronicdevice, enter a clock face selection mode of the electronic device, orenter a user interaction mode of the electronic device. In someembodiments, applications unit 3412 is configured to launch or runapplications with applications unit 3412. For example, applications unit3412 may be used for launching an application, running a launchedapplication, or setting a user reminder.

In some embodiments, the processing unit 3408 includes a displayenabling unit 3414, a detecting unit 3416, a determining unit 3418, andan accessing unit 3420. In some embodiments, the display enabling unit3414 is configured to cause a display of a user interface (or portionsof a user interface) in conjunction with the display unit 3402. Forexample, the display enabling unit 3414 may be used for displaying auser interface screen, updating a user interface screen, displaying aclock face, substituting one or more indications of an hourly timescalewith an indication of a first timescale for a stopwatch hand, animatinga stopwatch hand, rotating a simulation of the Earth (or Moon, or solarsystem), animating a user interface object, displaying an animatedreveal of a clock face, displaying a character user interface object,updating a displayed character user interface object (e.g., updating adisplayed character user interface object to indicate a second time orupdating a displayed character user interface object by changing avisual aspect of the displayed character user interface object),visually distinguishing a displayed clock face to indicate a clock faceedit mode, visually indicating an element of a clock face for editing,visually distinguishing a displayed clock face to indicate a clock faceselection mode, centering a clock face on the display, updating anaffordance to indicate a time of day, or substituting the display of afirst user interface screen with a second user interface screen. In someembodiments, the detecting unit 3416 is configured to detect and/orreceive user input, e.g., through the use of touch-sensitive surfaceunit 3404 or a rotatable input mechanism (e.g., 506 or 1540). Forexample, the detecting 3416 may be used for detecting a user input,receiving data representing a user input, receiving a user input,detecting a user movement of the device, detecting a contact on thetouch-sensitive display, detecting a swipe on the touch-sensitivedisplay, or detecting a movement of the rotatable input mechanism. Insome embodiments, the determining unit 3418 is configured to makedeterminations. For example, determining unit 3418 may be used fordetermining whether characteristic intensity of a contact on thetouch-sensitive display is above an intensity threshold or determiningwhether an event meets a condition. In some embodiments, the accessingunit 3420 is configured to access and/or select information. Forexample, accessing unit 3420 may be used for accessing a folder,selecting an image from the folder, accessing data representing apreviously displayed animated sequence, or selecting an animatedsequence. The units of FIG. 34 may be used to implement the varioustechniques and methods described above with respect to FIGS. 6-19.

The functional blocks of the device 3400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 34 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

In accordance with some embodiments, FIG. 35 shows an exemplaryfunctional block diagram of an electronic device 3500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3500 are configured to perform the techniques described above.The functional blocks of the device 3500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 35 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 35, an electronic device 3500 includes a display unit3502 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3504 configured to receive contacts,optionally, a location sensing unit 3518 configured to sense location,optionally, a movement detection unit 3520, and a processing unit 3506coupled to the display unit 3502, optionally, the touch-sensitivesurface unit 3504, optionally, the location sensing unit 3518, andoptionally, the movement detection unit 3520. In some embodiments, theprocessing unit 3506 includes a receiving unit 3508, a display enablingunit 3510, an update enabling unit 3512, an accessing unit 3514, and ananimation enabling unit 3516.

The processing unit 3506 is configured to receive (e.g., with receivingunit 3508) data representing a user input, and in response to receivingthe data: enable display (e.g., with display enabling unit 3510), on thedisplay unit (e.g., display unit 3502), of a user interface screen, theuser interface screen including a clock face indicating a first time,wherein the first time precedes a current time; and enable update (e.g.,with update enabling unit 3512), on the display unit (e.g., display unit3502), of the user interface screen by enabling animation (e.g., withanimation enabling unit 3516), on the display unit (e.g., display unit3502), of the clock face to transition from indicating the first time toindicating the current time, wherein the animation represents thepassage of time from the first time to the current time.

In some embodiments, the processing unit 3506 is further configured toreceive (e.g., with receiving unit 3508) second data representing a timeof a previous user movement of electronic device 3500, wherein theprevious user movement of electronic device 3500 is before receipt ofthe data representing the user input, and wherein the time of theprevious user movement of electronic device 3500 is the first timeindicated by the clock face. In some embodiments, the first timeprecedes the current time by a first duration, and wherein the firstduration is a predetermined duration before the current time. In someembodiments, the predetermined duration is 5 hours. In some embodiments,the first time is a predetermined time of day. In some embodiments, theclock face is animated for a period of time indicative of the firstduration. In some embodiments, the clock face is animated for a periodof time independent of the first duration. In some embodiments, theclock face comprises a representation of a digital clock including anumerical indication of an hour and a numerical indication of a minute.In some embodiments, the clock face comprises a representation of ananalog clock including an hour hand and a minute hand. In someembodiments, enabling animation (e.g., with animation enabling unit3516) of the first user interface object (e.g., on the user interfacescreen displayed on display unit 3502) comprises rotating one or more ofthe hour hand and the minute hand in a clockwise motion on-screen. Insome embodiments, the processing unit 3506 is further configured toaccess (e.g., with accessing unit 3514) an image of a scene, wherein theimage of the scene is representative of the time indicated by the clockface; and enable display (e.g., with display enabling unit 3510), on thedisplay unit (e.g., display unit 3502), of the image as a background onthe user interface screen. In some embodiments, the image of the sceneis an image captured at substantially the same time of day as the timeindicated by the clock face. In some embodiments, the processing unit3506 is further configured to access (e.g., with accessing unit 3514) afirst image of a scene, wherein the first image is representative of thefirst time; and access (e.g., with accessing unit 3514) a second imageof the scene, wherein the second image is representative of the currenttime; and in response to receiving (e.g., with receiving unit 3508) thedata representing the user input: enable successive display (e.g., withdisplay enabling unit 3510), on the display unit (e.g., display unit3502), of the first image of the scene and the second image of thescene, the successive display indicating the passage of time from thefirst time to the current time. In some embodiments, the first image ofthe scene and the second image of the scene are displayed as backgroundson the user interface screen. In some embodiments, the processing unit3506 is further configured to access (e.g., with accessing unit 3514) asequence of images of a scene, the sequence of images including: a firstimage of the scene, wherein the first image of the scene isrepresentative of the first time; one or more second images of thescene, wherein the one or more second images are representative of oneor more times between the first time and the current time, and whereinthe one or more second images are after the first image of the scenewithin the sequence of images; and a third image of the scene, whereinthe third image of the scene is representative of the current time, andwherein the third image of the scene is after the one or more secondimages of the scene within the sequence of images; and in response toreceiving (e.g., with receiving unit 3508) the data representing theuser input: enable display (e.g., with display enabling unit 3510), onthe display unit (e.g., display unit 3502), of the sequence of images ofthe scene as an animated sequence, wherein displaying the sequence ofimages comprises enabling animation (e.g., with animation enabling unit3516) of the sequence of images to indicate the passage of time from thefirst time to the current time. In some embodiments, the sequence ofimages of the scene is displayed as an animated background on the userinterface screen. In some embodiments, the scene is user-designated. Insome embodiments, electronic device 3500 further comprises a locationsensing unit (e.g., location sensing unit 3730), processing unit 3506 iscoupled to the location sensing unit (e.g., location sensing unit 3730),and the processing unit 3506 is further configured to enable obtaining acurrent location of electronic device 3500 from the location sensor(e.g., location sensing unit 3518), wherein the first image representsthe first time at the current location, and wherein the second image orthe third image represents the current time at the current location. Insome embodiments, the processing unit 3506 is further configured toenable display (e.g., with display enabling unit 3510), on the displayunit (e.g., display unit 3502), of a user interface object on the userinterface screen at a first position, wherein the first position of theuser interface object is based on the first time. In some embodiments,the processing unit 3506 is further configured to enable animation(e.g., with animation enabling unit 3516), on the display unit (e.g.,display unit 3502), of the user interface object by moving the userinterface object from the first position to a second position on theuser interface screen, wherein the second position is based on thecurrent time, and wherein moving the user interface object from thefirst position to a second position indicates the passage of time fromthe first time to the current time. In some embodiments, the userinterface object is a graphical representation of a sun. In someembodiments, the user interface object is a graphical representation ofa moon. In some embodiments, the electronic device 3500 further includesa movement detection unit (e.g., movement detection unit 3520), theprocessing unit 3506 is coupled to the movement detection unit, and theprocessing unit 3506 is further configured to: detect a movement of theelectronic device (e.g., with movement detection unit 3520), wherein theuser input comprises the movement of the electronic device 3500. In someembodiments, the user input is a contact on the touch-sensitive surfaceunit (e.g., touch-sensitive surface unit 3504).

The operations described above with reference to FIG. 20 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.35. For example, receiving operation 2002, displaying operation 2004,and updating operation 2006 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 36 shows an exemplaryfunctional block diagram of an electronic device 3600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3600 are configured to perform the techniques described above.The functional blocks of the device 3600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 36 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 36, an electronic device 3600 includes a display unit3602 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3604 configured to receive contacts,optionally, a rotatable input unit 3624 configured to receive rotatableinput (e.g., from a rotatable input mechanism), and a processing unit3606 coupled to the display unit 3602, optionally, the touch-sensitivesurface unit 3604, and optionally, the rotatable input unit 3624. Insome embodiments, the processing unit 3606 includes a receiving unit3608, a display enabling unit 3610, a substitution enabling unit 3612, acessation enabling unit 3614, an animation enabling unit 3616, alaunching unit 3618, a removal enabling unit 3620, and a translationenabling unit 3622.

The processing unit 3606 is configured to enable display (e.g., withdisplay enabling unit 3610), on the display unit (e.g., display unit3602), of a clock face that indicates current time, the clock faceincluding: a user interface object comprising an hour hand and a minutehand, wherein the user interface object indicates the current time; oneor more indications of an hourly timescale; and a stopwatch hand;receive data (e.g., with receiving unit 3608) representing a user input;and enable substitution (e.g., with substitution enabling unit 3612), onthe display unit (e.g., display unit 3602), of the one or moreindications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand; and enable animation (e.g., withanimation enabling unit 3616), on the display unit (e.g., display unit3602), of the stopwatch hand to reflect passage of time.

In some embodiments, the processing unit 3606 is further configured to,while enabling animation (e.g., with animation enabling unit 3616), onthe display unit (e.g., display unit 3602), of the stopwatch hand toreflect the passage of time, receive second data (e.g., with receivingunit 3608) representing a second user input; and in response toreceiving the second data: enable cessation (e.g., with cessationenabling unit 3614), on the display unit (e.g., display unit 3602) ofthe animation of the stopwatch hand. In some embodiments, the processingunit 3606 is further configured to enable display (e.g., with displayenabling unit 3610), on the display unit (e.g., display unit 3602), of afirst affordance, the first affordance representing a start/stopfunction, wherein the first data representing the first user input andthe second data representing the second user input both representcontacts on the displayed first affordance. In some embodiments, theprocessing unit 3606 is further configured to enable display (e.g., withdisplay enabling unit 3610), on the display unit (e.g., display unit3602), of a second affordance, the second affordance representing a lapfunction; receive third data (e.g., with receiving unit 3608)representing a contact on the displayed second affordance, wherein thethird data is received after receiving the first data and beforereceiving the second data; and enable display (e.g., with displayenabling unit 3610), on the display unit (e.g., display unit 3602), of athird numerical indication of elapsed time between receiving the firstdata and receiving the third data. In some embodiments, the processingunit 3606 is further configured to enable display (e.g., with displayenabling unit 3610), on the display unit (e.g., display unit 3602), of athird affordance, the third affordance representing a stopwatchapplication; receive fourth data (e.g., with receiving unit 3608)representing a contact on the displayed third affordance; and inresponse to receiving the fourth data: launch (e.g., with launching unit3618) the stopwatch application. In some embodiments, the firsttimescale for the stopwatch hand is 60 seconds. In some embodiments, thefirst timescale for the stopwatch hand is 30 seconds. In someembodiments, the first timescale for the stopwatch hand is 6 seconds. Insome embodiments, the first timescale for the stopwatch hand is 3seconds. In some embodiments, movement of the stopwatch hand is animatedat a rate based on the first timescale for the stopwatch hand. In someembodiments, enabling substitution (e.g., with substitution enablingunit 3612), on the display unit (e.g., display unit 3602), of the one ormore indications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand comprises: enabling removal (e.g., withremoval enabling unit 3620), on the display unit (e.g., display unit3602), of the one or more indications of the hourly timescale; enablingdisplay (e.g., with display enabling unit 3610), on the display unit(e.g., display unit 3602), of the indication of the first timescale forthe stopwatch hand; and enabling translation (e.g., with translationenabling unit 3622), on the display unit (e.g., display unit 3602), ofthe displayed indication of the first timescale for the stopwatch handin a rotational motion, wherein the rotational motion is in a clockwisedirection. In some embodiments, electronic device 3600 further comprisesa rotatable input unit (e.g., rotatable input unit 3624), wherein theprocessing unit is coupled to the rotatable input unit (e.g., rotatableinput unit 3624), and processing unit 3606 is further configured toreceive fifth data representing a rotatable input from the rotatableinput unit (e.g., with rotatable input unit 3624); and enablesubstitution (e.g., with substitution enabling unit 3612), on thedisplay unit (e.g., display unit 3602) of the indication of the firsttimescale for the stopwatch hand with an indication of a secondtimescale for the stopwatch hand, wherein the second timescale isdifferent from the first timescale. In some embodiments, enablingsubstitution (e.g., with substitution enabling unit 3612), on thedisplay unit (e.g., display unit 3602) of the indication of the firsttimescale for the stopwatch hand with the indication of the secondtimescale for the stopwatch hand comprises: enabling removal (e.g., withremoval enabling unit 3620), on the display unit (e.g., display unit3602), of the indication of the first timescale for the stopwatch hand;enabling display (e.g., with display enabling unit 3610), on the displayunit (e.g., display unit 3602) of the indication of the second timescalefor the stopwatch hand; and enabling translation (e.g., with translationenabling unit 3622), on the display unit (e.g., display unit 3602), ofthe displayed indication of the second timescale for the stopwatch handin a rotational motion, wherein the rotational motion is in a clockwisedirection. In some embodiments, the processing unit 3606 is furtherconfigured to after receiving the first data representing the first userinput: enable animation (e.g., with animation enabling unit 3616), onthe display unit (e.g., display unit 3602), of the stopwatch hand torepresent a rotational motion about an origin; and enable cessation(e.g., with cessation enabling unit 3614), on the display unit (e.g.,display unit 3602), of the animation to display the stopwatch hand at aposition at π/2 radians relative to the rotational motion about theorigin.

The operations described above with reference to FIG. 21 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.36. For example, displaying operation 2102, receiving operation 2104,and substituting operation 2106 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 37 shows an exemplaryfunctional block diagram of an electronic device 3700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3700 are configured to perform the techniques described above.The functional blocks of the device 3700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 37 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 37, an electronic device 3700 includes a display unit3702 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3704 configured to receive contacts,optionally, a rotatable input unit 3728 configured to receive rotatableinput (e.g., from a rotatable input mechanism), optionally, a locationsensing unit 3730 configured to sense location, and a processing unit3706 coupled to the display unit 3702, optionally, the touch-sensitivesurface unit 3704, optionally, the rotatable input unit 3728, andoptionally, the location sensing unit 3730. In some embodiments, theprocessing unit 3706 includes a receiving unit 3708, a display enablingunit 3710, a rotation enabling unit 3712, an update enabling unit 3714,a detecting unit 3716, an animation enabling unit 3718, a visualdistinguishment enabling unit 3720, a removal enabling unit 3722, areplacement enabling unit 3724, and a determining unit 3726.

The processing unit 3706 is configured to enable display (e.g., withdisplay enabling unit 3710), on the display unit (e.g., display unit3702), of a user interface screen, the user interface screen including:a first affordance representing a simulation of a first region of theEarth as illuminated by the Sun at a current time; and a secondaffordance indicating the current time; receive (e.g., with receivingunit 3708) a user input; and in response to receiving the user input:enable rotation (e.g., with rotation enabling unit 3712), on the displayunit (e.g., display unit 3702), of the simulation of the Earth todisplay a second region of the Earth as illuminated by the Sun at thecurrent time.

In some embodiments, the first affordance representing the simulation ofthe first region of the Earth as illuminated by the Sun at the currenttime comprises a representation of a solar terminator. In someembodiments, the user input comprises a swipe on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 3704) in a first swipedirection. In some embodiments, the simulation of the first region ofthe Earth is rotated in a first direction of rotation, and theprocessing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a second user input; and in response to receivingthe second user input: enable rotation (e.g., with rotation enablingunit 3712), on the display unit (e.g., display unit 3702), of thesimulation of the first region of the Earth in a second direction ofrotation, wherein the second direction of rotation and the firstdirection of rotation are different. In some embodiments, the seconduser input comprises a swipe on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 3704) in a second swipe direction, and thefirst swipe direction and the second swipe direction are different. Insome embodiments, electronic device 3700 further comprises a rotatableinput unit (e.g., rotatable input unit 3728), wherein the processingunit 3706 is coupled to the rotatable input unit, and wherein theprocessing unit 3706 is further configured to: receive a third userinput representing a rotatable input from the rotatable input unit(e.g., rotatable input unit 3728) and in response to receiving the thirduser input: enable update (e.g., with update enabling unit 3714), on thedisplay unit (e.g., display unit 3702), of the first affordance torepresent a simulation of the first region of the Earth as illuminatedby the Sun at a non-current time. In some embodiments, the processingunit 3706 is further configured to: enable update (e.g., with updateenabling unit 3714), on the display unit (e.g., display unit 3702), ofthe second affordance to indicate the non-current time. In someembodiments, electronic device 3700 further comprises a location sensingunit (e.g., location sensing unit 3730), wherein the processing unit3706 is coupled to the location sensing unit, and wherein the processingunit 3706 is further configured to: before displaying the user interfacescreen, obtain a current location of electronic device 3700 from thelocation sensing unit (e.g., location sensing unit 3730), wherein thedisplayed first region of the Earth represented by the first affordanceindicates the current location of electronic device 3700. In someembodiments, the processing unit 3706 is further configured to: detect(e.g., with detecting unit 3716) a user movement of electronic device3700; and in response to detecting the user movement: enable animation(e.g., with animation enabling unit 3718), on the display unit (e.g.,display unit 3702), of the first affordance representing the simulationof the Earth by translating the first affordance on-screen towards thecenter of the displayed user interface screen. In some embodiments, theprocessing unit 3706 is further configured to: enable display (e.g.,with display enabling unit 3710), on the display unit (e.g., displayunit 3702), of a third affordance, the third affordance representing amoon; detect (e.g., with detecting unit 3716) a contact on the displayedthird affordance on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 3704), and in response to detecting thecontact: enable update (e.g., with update enabling unit 3714), on thedisplay unit (e.g., display unit 3702), of the user interface screen,wherein enabling update of the display of the user interface screencomprises: enabling display (e.g., with display enabling unit 3710), onthe display unit (e.g., display unit 3702), of a fourth affordancerepresenting a simulation of the Moon, the fourth affordancerepresenting a simulation of the Moon as seen from the Earth at thecurrent time; and enabling display (e.g., with display enabling unit3710), on the display unit (e.g., display unit 3702), of a fifthaffordance indicating the current time. In some embodiments, enablingupdate (e.g., with update enabling unit 3714), on the display unit(e.g., display unit 3702), of the user interface screen comprisesenabling animation (e.g., with animation enabling unit 3718), on thedisplay unit (e.g., display unit 3702), of the first affordancerepresenting the simulation of the first region of the Earth asilluminated by the Sun by zooming out. In some embodiments, theprocessing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a fourth user input; and in response to receivingthe fourth user input: enable rotation (e.g., with rotation enablingunit 3712), on the display unit (e.g., display unit 3702), of thesimulation of the Moon to display the Moon as seen from the Earth at anon-current time; and enable update (e.g., with update enabling unit3714), on the display unit (e.g., display unit 3702), of the fifthaffordance to indicate the non-current time. In some embodiments, thefourth user input comprises a swipe on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 3704) in a first swipe direction. Insome embodiments, the simulation of the Moon as seen from the Earth isrotated in a first direction of rotation, and the processing unit 3706is further configured to: receive (e.g., with receiving unit 3708) afifth user input; and in response to receiving the fifth user input:enable rotation (e.g., with rotation enabling unit 3712), on the displayunit (e.g., display unit 3702), of the simulation of the Moon as seenfrom the Earth in a second direction of rotation, wherein the seconddirection of rotation and the first direction of rotation are different.In some embodiments, the fifth user input comprises a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704)in a second swipe direction, and the first swipe direction and thesecond swipe direction are different. In some embodiments, electronicdevice 3700 further comprises a rotatable input unit (e.g., rotatableinput unit 3728), the processing unit 3706 is coupled to the rotatableinput unit, and receiving the fourth user input comprises receiving arotatable input from the rotatable input unit (e.g., rotatable inputunit 3728) in a first direction of rotation. In some embodiments,electronic device 3700 further comprises a rotatable input unit (e.g.,rotatable input unit 3728), the processing unit 3706 is coupled to therotatable input unit, and the simulation of the Moon as seen from theEarth is rotated in a first direction of rotation, wherein theprocessing unit is further configured to: receive (e.g., with receivingunit 3708) a sixth user input; and in response to receiving the sixthuser input: enable rotation (e.g., with rotation enabling unit 3712), onthe display unit (e.g., display unit 3702), of the simulation of theMoon as seen from the Earth in a second direction of rotation, whereinthe second direction of rotation and the first direction of rotation aredifferent. In some embodiments, the sixth user input comprises arotatable input from the rotatable input unit (e.g., rotatable inputunit 3728) in a second direction of rotation, and wherein the firstdirection of rotation and the second direction of rotation aredifferent. In some embodiments, the processing unit 3706 is furtherconfigured to: detect (e.g., with detecting unit 3716) a user double tapon the touch-sensitive surface unit (e.g., touch-sensitive surface unit3704), the user double tap comprising a first contact on thetouch-sensitive surface unit and a second contact on the touch-sensitivesurface unit; determine (e.g., with determining unit 3726) whether thefirst contact and the second contact were received within apredetermined interval; and in response to detecting the user doubletap, and in accordance with a determination that the first contact andthe second contact were received within the predetermined interval:enable display (e.g., with display enabling unit 3710), on the displayunit (e.g., display unit 3702), of additional lunar information. In someembodiments, the processing unit 3706 is further configured to: enabledisplay (e.g., with display enabling unit 3710), on the display unit(e.g., display unit 3702), of a sixth affordance on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 3704), the sixthaffordance representing a solar system; detect (e.g., with detectingunit 3716) a contact on the displayed sixth affordance, and in responseto detecting the contact: enable update (e.g., with update enabling unit3714), on the display unit (e.g., display unit 3702), of the userinterface screen, wherein enabling update (e.g., with update enablingunit 3714), on the display unit (e.g., display unit 3702), of the userinterface screen comprises: enabling display (e.g., with displayenabling unit 3710), on the display unit (e.g., display unit 3702), of aseventh affordance representing a solar system, the seventh affordancecomprising representations of the Sun, the Earth, and one or morenon-Earth planets at their respective positions at a current time; andenabling display (e.g., with display enabling unit 3710), on the displayunit (e.g., display unit 3702), of an eighth affordance indicating thecurrent time. In some embodiments, enabling update (e.g., with updateenabling unit 3714), on the display unit (e.g., display unit 3702), ofthe user interface screen comprises enabling animation (e.g., withanimation enabling unit 3718), on the display unit (e.g., display unit3702), of the first affordance representing the simulation of the firstregion of the Earth as illuminated by the Sun or enabling animation(e.g., with animation enabling unit 3718), on the display unit (e.g.,display unit 3702), of the fourth affordance representing a simulationof the Moon as seen from the Earth by zooming out. In some embodiments,the processing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a seventh user input; and in response to receivingthe seventh user input: enable update (e.g., with update enabling unit3714), on the display unit (e.g., display unit 3702), of the seventhaffordance to depict respective positions of the Sun, the Earth, and theone or more non-Earth planets for a non-current time, wherein updatingthe seventh affordance comprises rotating the Earth and the one or morenon-Earth planets about the Sun; and enable update (e.g., with updateenabling unit 3714), on the display unit (e.g., display unit 3702), ofthe eighth affordance to indicate the non-current time. In someembodiments, the seventh user input comprises a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704)in a first swipe direction. In some embodiments, the Earth and the oneor more non-Earth planets are rotated about the Sun in a first directionof rotation, and the processing unit 3706 is further configured to:receive (e.g., with receiving unit 3708) an eighth user input; and inresponse to receiving the eighth user input: enable rotation (e.g., withrotation enabling unit 3712), on the display unit (e.g., display unit3702), of the Earth and the one or more non-Earth planets about the Sunin a second direction of rotation, wherein the second direction ofrotation and the first direction of rotation are different. In someembodiments, the eighth user input comprises a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704)in a second swipe direction, and wherein the first swipe direction andthe second swipe direction are different. In some embodiments,electronic device 3700 further comprises a rotatable input unit (e.g.,rotatable input unit 3728), the processing unit 3706 is coupled to therotatable input unit (e.g., rotatable input unit 3728), and receivingthe seventh user input comprises receiving a rotatable input from therotatable input unit (e.g., rotatable input unit 3728) in a firstdirection of rotation. In some embodiments, electronic device 3700further comprises a rotatable input unit (e.g., rotatable input unit3728), the processing unit 3706 is coupled to the rotatable input unit,wherein the Earth and the one or more non-Earth planets are rotatedabout the Sun in a first direction of rotation, and the processing unit3706 is further configured to: receive (e.g., with receiving unit 3708)a ninth user input; and in response to receiving the ninth user input:enable rotation (e.g., with rotation enabling unit 3712), on the displayunit (e.g., display unit 3702), of the Earth and the one or morenon-Earth planets about the Sun in a second direction of rotation,wherein the second direction of rotation and the first direction ofrotation are different. In some embodiments, the ninth user inputcomprises a rotatable input from the rotatable input unit (e.g.,rotatable input unit 3728) in a second direction of rotation, andwherein the first direction of rotation and the second direction ofrotation are different. In some embodiments, the representation of theEarth further comprises a representation of the orbit of the Eartharound the Sun, and wherein the representation of the one or morenon-Earth planets further comprises a representation of the orbit of theone or more non-Earth planets around the Sun. In some embodiments, theprocessing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a tenth user input comprising a contact on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704),wherein the contact is associated with the representation of the Earthor the representation of the one or more non-Earth planets, the contacton the touch-sensitive surface unit having an associated duration; whilecontinuing to receive the contact, determine (e.g., with determiningunit 3726) whether the duration of the contact exceeds a predeterminedthreshold; in response to receiving the tenth user input, and inaccordance with a determination that the duration of the contact exceedsthe predetermined threshold: enable visual distinguishment (e.g., withvisual distinguishment enabling unit 3720), on the display unit (e.g.,display unit 3702), of the representation of the Earth or therepresentation of the one or more non-Earth planets associated with thecontact; detect (e.g., with detecting unit 3716) a break in the contact;and in response to detecting the break in the contact: enable display(e.g., with display enabling unit 3710), on the display unit (e.g.,display unit 3702), of information about the Earth or the one or morenon-Earth planets associated with the contact. In some embodiments, theprocessing unit 3706 is further configured to: after enabling display,on the display unit, of the information about the Earth or the one ormore non-Earth planets associated with the contact, receive (e.g., withreceiving unit 3708) an eleventh user input; determine (e.g., withdetermining unit 3732) whether the eleventh user input represents a tapor a swipe on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 3704); in accordance with a determination that the eleventhuser input represents a tap: enable removal (e.g., with removal enablingunit 3724), on the display unit (e.g., display unit 3702), of thedisplayed information about the Earth or the one or more non-Earthplanets; and in accordance with a determination that the eleventh userinput represents a swipe: enable replacement (e.g., with replacementenabling unit 3724), on the display unit (e.g., display unit 3702), ofthe displayed information about the Earth or the one or more non-Earthplanets with information about a second planet selected from the groupconsisting of the Earth and the one or more non-Earth planets, whereinthe second planet is not the planet associated with the contact.

The operations described above with reference to FIG. 22 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.37. For example, displaying operation 2202, receiving operation 2204,and rotating operation 2206 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 38 shows an exemplaryfunctional block diagram of an electronic device 3800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3800 are configured to perform the techniques described above.The functional blocks of the device 3800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 38 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 38, an electronic device 3800 includes a display unit3802 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3804 configured to receive contacts,optionally, a rotatable input unit 3820 configured to receive rotatableinput (e.g., from a rotatable input mechanism), optionally, a locationsensing unit 3822 configured to sense location, optionally, an audiounit 3826, optionally, a haptic unit 3828, and a processing unit 3806coupled to the display unit 3802, optionally, the touch-sensitivesurface unit 3804, optionally, the rotatable input unit 3820,optionally, the location sensing unit 3822, optionally, the audio unit3826, and optionally, the haptic unit 3828. In some embodiments, theprocessing unit 3806 includes a receiving unit 3808, a display enablingunit 3810, a translation enabling unit 3812, an update enabling unit3814, a determining unit 3816, a setting unit 3818, and a detecting unit3824.

The processing unit 3806 is configured to enable display (e.g., withdisplay enabling unit 3810), on the display unit (e.g., display unit3802), of a user interface screen, the user interface screen comprising:a first portion of the user interface screen, the first portionindicating daytime; a second portion of the user interface screen, thesecond portion indicating nighttime; a user interface object, the userinterface object representing a sinusoidal wave with a periodrepresenting a day, wherein the sinusoidal wave indicates a path of theSun through the day, and wherein the sinusoidal wave is displayed in oneor more of the first portion and the second portion; a first affordancerepresenting the Sun, wherein the first affordance is displayed at afirst position on the displayed sinusoidal wave, the first positionindicating a current time of the day and whether the current time of theday is during daytime or nighttime; and a second affordance, the secondaffordance indicating the current time of day.

In some embodiments, electronic device 3800 further comprises a locationsensing unit (e.g., location sensing unit 3822), processing unit 3806 iscoupled to the location sensing unit (e.g., location sensing unit 3822),and processing unit 3806 is further configured to: obtain a currentlocation of the electronic device from the location sensing unit (e.g.,with location sensing unit 3822), wherein the ratio of the displayedfirst portion indicating daytime relative to the second portionindicating nighttime indicates daylight hours at the current location atthe current time. In some embodiments, amplitude of the sinusoidal waveis based on height of the Sun relative to horizon at the currentlocation and at the current time. In some embodiments, the processingunit 3806 is further configured to: enable display (e.g., with displayenabling unit 3810), on the display unit (e.g., display unit 3802), of aline on the user interface screen, wherein the line divides the firstportion of the user interface screen indicating daytime and the secondportion of the user interface screen indicating nighttime, wherein theline intersects the sinusoidal wave at a first point representingsunrise and at a second point representing sunset. In some embodiments,the processing unit 3806 is further configured to: receive (e.g., withreceiving unit 3808) a user contact on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 3804) at the first affordance, thefirst affordance displayed at the first position on the displayedsinusoidal wave, the first position indicating the current time; whilecontinuing to receive the user contact, detect (e.g., with detectingunit 3824) movement (e.g., on touch-sensitive surface unit 3804) of theuser contact from the first position to a second position on thedisplayed sinusoidal wave without a break in contact of the user contacton the touch-sensitive surface unit, the second position on thedisplayed sinusoidal wave indicating a non-current time; and in responseto detecting the contact at the second position: enable translation(e.g., with translation enabling unit 3812), on the display unit (e.g.,display unit 3802), of the first affordance on-screen from the firstposition on the displayed sinusoidal wave to the second position on thedisplayed sinusoidal wave, wherein the translation tracks the displayedsinusoidal wave; and enable update (e.g., with update enabling unit3814), on the display unit (e.g., display unit 3802), of the secondaffordance to indicate the non-current time. In some embodiments, theprocessing unit 3806 is further configured to: in response to detectingthe contact at the first affordance: enable display (e.g., with displayenabling unit 3810), on the display unit (e.g., display unit 3802), of,on the user interface screen: a third user interface object, wherein thethird user interface object is displayed at the first point along thesinusoidal wave representing sunrise; and a fourth user interfaceobject, wherein the fourth user interface object is displayed at thesecond point along the sinusoidal wave representing sunset. In someembodiments, the processing unit 3806 is further configured to: inresponse to detecting (e.g., with detecting unit 3824) the contact atthe first affordance (e.g., on touch-sensitive surface unit 3804):enable display (e.g., with display enabling unit 3810), on the displayunit (e.g., display unit 3802), of, on the user interface screen: afifth user interface object, wherein the fifth user interface object isdisplayed along the sinusoidal wave at a third point representing dawn;and a sixth user interface object, wherein the sixth user interfaceobject is displayed along the sinusoidal wave at a fourth pointrepresenting dusk. In some embodiments, the processing unit 3806 isfurther configured to: detect (e.g., with detecting unit 3824) a breakin contact of the user contact on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 3804), and in response to detectingthe break in contact of the user contact on the touch-sensitive surfaceunit: enable translation (e.g., with translation enabling unit 3812), onthe display unit (e.g., display unit 3802), of the first affordanceon-screen from the second position to the first position, wherein thetranslation tracks the displayed sinusoidal wave; and enable update(e.g., with update enabling unit 3814), on the display unit (e.g.,display unit 3802), of the second affordance to indicate the currenttime of day. In some embodiments, the first affordance representing thesun appears filled when the first affordance is displayed at a positionfully within the first portion of the user interface screen. In someembodiments, the first affordance representing the sun appears hollowwhen the first affordance is displayed at a position fully within thesecond portion of the user interface screen. In some embodiments, thefirst affordance representing the sun appears half-filled when the firstaffordance is displayed at a position intersecting both the firstportion and the second portion of the user interface screen. In someembodiments, the processing unit 3806 is further configured to:determine (e.g., with determining unit 3816) whether the position of thefirst affordance on the displayed sinusoidal wave intersects with aposition of the second affordance indicating the current time of day;and in accordance with a determination that the position of the firstaffordance on the displayed sinusoidal wave intersects with a positionof the second affordance indicating the current time of day: enabledisplay (e.g., with display enabling unit 3810), on the display unit(e.g., display unit 3802), of the second affordance at a second positionthat does not intersect the position of the displayed sinusoidal wave.In some embodiments, the processing unit 3806 is further configured to:detect (e.g., with detecting unit 3824) a user input; and in response todetecting the user input: enable display (e.g., with display enablingunit 3810), on the display unit (e.g., display unit 3802), of a seconduser interface screen, the second user interface screen comprising anindication of a time of sunrise and an indication of a time of sunset.In some embodiments, the electronic device 3800 further comprises arotatable input unit (e.g., rotatable input unit 3820), the processingunit 3806 is coupled to the rotatable input unit, and the processingunit 3806 is further configured to: detect (e.g., with detecting unit3824) a movement corresponding to a rotatable input from the rotatableinput unit (e.g., rotatable input unit 3820); and in response todetecting the movement: enable translation (e.g., with translationenabling unit 3812), on the display unit (e.g., display unit 3802), ofthe first affordance representing the Sun to a third position on thedisplayed sinusoidal wave, wherein the third position indicates a thirdtime of day, wherein the third time of day is not the current time ofday; detect (e.g., with detecting unit 3824) a contact on thetouch-sensitive surface unit (e.g., with touch-sensitive surface unit3804) on the displayed first affordance at the third position; and inresponse to detecting the contact: set (e.g., with setting unit 3818) auser reminder for the third time of day. In some embodiments, settingthe user reminder for the third time of day comprises: enabling display,on the display unit (e.g., display unit 3802), of a third affordance onthe display, the third affordance representing a user prompt to set analert for the third time of day.

In some embodiments, the processing unit 3806 is further configured toenable display (e.g., with display enabling unit 3810), on the displayunit (e.g., display unit 3802), of a visual alert for the third time ofday, and the user reminder for the third time of day comprises thevisual alert for the third time of day. In some embodiments, theelectronic device 3800 further comprises an audio unit (e.g., audio unit3826), the processing unit 3806 is coupled to the audio unit, theprocessing unit 3806 is further configured to enable an audio alert forthe third time of day via the audio unit (e.g., with audio unit 3826),and the user reminder for the third time of day comprises the audioalert for the third time of day. In some embodiments, the electronicdevice 3800 further comprises a haptic unit (e.g., haptic unit 3828),the processing unit 3806 is coupled to the haptic unit, the processingunit 3806 is further configured to enable a haptic alert for the thirdtime of day via the haptic unit (e.g., with haptic unit 3828), and theuser reminder for the third time of day comprises the haptic alert forthe third time of day.

The operations described above with reference to FIG. 23 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.38. For example, displaying operation 2302, optional receiving operation2304, and optional detecting operation 2306 may be implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 39 shows an exemplaryfunctional block diagram of an electronic device 3900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3900 are configured to perform the techniques described above.The functional blocks of the device 3900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 39 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 39, an electronic device 3900 includes a display unit3902 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3904 configured to receive contacts,optionally, a wireless communication unit 3912 configured to send and/orreceive wireless communication, and a processing unit 3906 coupled tothe display unit 3902, optionally, the touch-sensitive surface unit3904, and optionally, the wireless communication unit 3912. In someembodiments, the processing unit 3906 includes a receiving unit 3908 anda display enabling unit 3910.

The processing unit 3906 is configured to enable display (e.g., withdisplay enabling unit 3910), on the display unit (e.g., display unit3902), of a user interface screen, the user interface screen including:a background based on an image, the background comprising a plurality ofpixels, wherein a subset of the pixels are modified in appearancerelative to the image such that the subset of pixels represents one ormore of: a first user interface object indicating a date; and a seconduser interface object indicating a time of day.

In some embodiments, the subset of the pixels is modified by colorblending. In some embodiments, the subset of the pixels is modified bycolor blurring. In some embodiments, the subset of the pixels ismodified in appearance relative to the image such that the subset ofpixels represents the first user interface object indicating the date.In some embodiments, the subset of the pixels is modified in appearancerelative to the image such that the subset of pixels represents thesecond user interface object indicating the time of day. In someembodiments, one of the first user interface object indicating the dateand the second user interface object indicating the time of day is afirst color independent of the background. In some embodiments, theprocessing unit 3906 is further configured to: receive (e.g., withreceiving unit 3908) data representing a background color of thebackground at a position of the displayed first user interface object orthe displayed second user interface object, wherein the first color isdifferent from the background color at the position of the displayedfirst user interface object or the displayed second user interfaceobject. In some embodiments, the image is a photo. In some embodiments,the image is stored on the electronic device. In some embodiments,wherein the electronic device 3900 further comprises a wirelesscommunication unit (e.g., wireless communication unit 3912), wherein theprocessing unit 3906 is coupled to the wireless communication unit, andthe image is stored on an external device coupled to electronic device3900 via the wireless communication unit (e.g., wireless communicationunit 3912). In some embodiments, the processing unit 3906 is furtherconfigured to: before enabling display (e.g., with display enabling unit3910), on the display unit (e.g., display unit 3902), of the userinterface screen: enable receipt (e.g., with receiving unit 3908), viathe wireless communication unit (e.g., wireless communication unit 3912)of data representing the background from the external device. In someembodiments, the processing unit 3906 is further configured to: enablereceipt (e.g., with receiving unit 3908), via the wireless communicationunit (e.g., wireless communication unit 3912) of data representing acurrent background of the external device, and enable display (e.g.,with display enabling unit 3910), on the display unit (e.g., displayunit 3902), of a second user interface screen on the display, the seconduser interface screen including: a second background, wherein the secondbackground corresponds with the current background of the externaldevice, the second background comprising a second plurality of pixels,wherein a second subset of the pixels are modified in appearancerelative to the current background of the external device such that thesecond subset of pixels represents one or more of: a third userinterface object indicating the date; and a fourth user interface objectindicating the time of day.

The operations described above with reference to FIG. 24 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.39. For example, displaying operation 2402 and optional receivingoperation 2404 may be implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub event, such as activation of anaffordance on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 may utilize or call data updater 176 or object updater 177to update the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 40 shows an exemplaryfunctional block diagram of an electronic device 4000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4000 are configured to perform the techniques described above.The functional blocks of the device 4000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 40 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 40, an electronic device 4000 includes a display unit4002 configured to display a graphic user interface, optionally, awireless communication unit 4004 configured to send and/or receivewireless communications, and a processing unit 4006 coupled to thedisplay unit 4002, and optionally, the wireless communication unit 4004.In some embodiments, device 4000 may further include a touch-sensitivesurface unit configured to receive contacts and coupled to theprocessing unit 4006. In some embodiments, the processing unit 4006includes a receiving unit 4008, a display enabling unit 4010, anaccessing unit 4012, a selecting unit 4014, an obtaining unit 4016, anda preventing unit 4018.

The processing unit 4006 is configured to access (e.g., with accessingunit 4012) a folder, the folder including two or more images; select(e.g., with selecting unit 4014) from the folder a first image; andenable display (e.g., with display enabling unit 4010), on the displayunit (e.g., display unit 4002), of a user interface screen, the userinterface screen comprising: a background based on the first image, thebackground comprising a plurality of pixels, wherein a subset of thepixels are modified in appearance relative to the image such that thesubset of pixels represents one or more of: a first user interfaceobject indicating a date; and a second user interface object indicatinga time of day.

In some embodiments, the subset of the pixels is modified by colorblending. In some embodiments, the subset of the pixels is modified bycolor blurring. In some embodiments, the subset of the pixels ismodified in appearance relative to the image such that the subset ofpixels represents the first user interface object indicating the date.In some embodiments, the subset of the pixels is modified in appearancerelative to the image such that the subset of pixels represents thesecond user interface object indicating the time of day. In someembodiments, one of the first user interface object indicating the dateand the second user interface object indicating the time of day is afirst color independent of the background. In some embodiments, theprocessing unit 4006 is further configured to: receive (e.g., withreceiving unit 4008) data representing a background color of thebackground at a position of the displayed first user interface object orthe displayed second user interface object, wherein the first color isdifferent from the background color at the position of the displayedfirst user interface object or the displayed second user interfaceobject. In some embodiments, the processing unit 4006 is furtherconfigured to: after enabling display, on the display unit, of the firstuser interface screen, receive (e.g., with receiving unit 4008) firstdata representing a user input, and in response to receiving the firstdata representing the user input: obtain (e.g., with obtaining unit4016) second data representing the displayed first background; select(e.g., with selecting unit 4014) a second image from the folder, whereinthe second image is different from the first image; and enable display(e.g., with display enabling unit 4010), on the display unit (e.g.,display unit 4002), of a second user interface screen, the second userinterface screen comprising: a second background based on the secondimage, the second background comprising a second plurality of pixels,wherein a second subset of the pixels are modified in appearancerelative to the second image such that the second subset of pixelsrepresents one or more of: a third user interface object indicating adate; and a fourth user interface object indicating a time of day. Insome embodiments, the processing unit 4006 is further configured to:receive (e.g., with receiving unit 4008) data representing a userprohibition of a third image from the folder; and in response toreceiving the data: prevent (e.g., with preventing unit 4018) thedisplay, on the display unit (e.g., display unit 4002), of the thirdimage as a third background in response to a future user input. In someembodiments, at least one of the first background, the secondbackground, and the third background is a photo. In some embodiments,the folder is stored on the electronic device 4000. In some embodiments,the electronic device 4000 further includes a wireless communicationunit (e.g., wireless communication unit 4004), the processing unit 4006is coupled to the wireless communication unit, and the folder is storedon an external device coupled to the electronic device 4000 via thewireless communication unit (e.g., wireless communication unit 4004). Insome embodiments, accessing the folder comprises: receiving (e.g., withreceiving unit 4008), via the wireless communication unit (e.g.,wireless communication unit 4004), data representing at least one of thetwo or more backgrounds.

The operations described above with reference to FIG. 25 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.40. For example, accessing operation 2502, selecting operation 2504, anddisplaying operation 2506 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 41 shows an exemplaryfunctional block diagram of an electronic device 4100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4100 are configured to perform the techniques described above.The functional blocks of the device 4100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 41 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 41, an electronic device 4100 includes a display unit4102 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4104 configured to receive contacts,optionally, a movement detection unit 4120 configured to detectmovement, and a processing unit 4106 coupled to the display unit 4102,optionally, the touch-sensitive surface unit 4104 and optionally, themovement detection unit 4120. In some embodiments, the processing unit4106 includes a detecting unit 4108, a display enabling unit 4110, ananimation enabling unit 4112, a selecting unit 4114, an accessing unit4116, and a substitution enabling unit 4118.

The processing unit 4106 is configured to detect (e.g., with detectingunit 4108) a user input, wherein the user input is detected at a firsttime, and in response to detecting the user input: enable display (e.g.,with display enabling unit 4110), on the display unit (e.g., displayunit 4102), of a user interface screen, the user interface screenincluding: a first user interface object indicating the first time; anda second user interface object; and enable animation (e.g., withanimation enabling unit 4112), on the display unit (e.g., display unit4102), of the second user interface object, the animation comprising asequential display of a first animated sequence, a second animatedsequence after the first animated sequence, and a third animatedsequence after the second animated sequence, wherein the first animatedsequence, the second animated sequence, and the third animated sequenceare different; after enabling animation of the second user interfaceobject, detect (e.g., with detecting unit 4108) a second user input,wherein the second user input is detected at a second time, wherein thesecond time is after the first time, and in response to detecting thesecond user input: access (e.g., with accessing unit 4116) datarepresenting the previously displayed second animated sequence; select(e.g., with selecting unit 4114) a fourth animated sequence, wherein thefourth animated sequence is different from the first animated sequenceand the second animated sequence; enable display (e.g., with displayenabling unit 4110), on the display unit (e.g., display unit 4102), of asecond user interface screen, the second user interface screenincluding: the first user interface object, wherein the first userinterface object is updated to indicate the second time; and a thirduser interface object related to the second user interface object; andenable animation (e.g., with animation enabling unit 4112), on thedisplay unit (e.g., display unit 4102), of the third user interfaceobject, the animation comprising a sequential display of the firstanimated sequence, the fourth animated sequence after the first animatedsequence, and the third animated sequence after the fourth animatedsequence.

In some embodiments, the third animated sequence is based on a reversesequence of the first animated sequence. In some embodiments, theelectronic device 4100 further comprises a movement detection unit(e.g., movement detection unit 4120), wherein the processing unit 4106is coupled to the movement detection unit, and wherein the processingunit 4106 is further configured to enable detection of a movement of theelectronic device via the movement detection unit (e.g., movementdetection unit 4120), and wherein the user input represents a usermovement of the electronic device 4100. In some embodiments, theelectronic device 4100 further comprises a movement detection unit(e.g., movement detection unit 4120), wherein the processing unit 4106is coupled to the movement detection unit, and wherein the processingunit 4106 is further configured to enable detection of a movement of theelectronic device via the movement detection unit (e.g., movementdetection unit 4120), and wherein the second user input represents asecond user movement of the electronic device 4100. In some embodiments,the second user interface object and the third user interface object arethe same. In some embodiments, the third user interface object is areflection of the second user interface object. In some embodiments, thefourth animated sequence comprises a reflection of the second animatedsequence about a horizontal axis. In some embodiments, the fourthanimated sequence comprises a reflection of the second animated sequenceabout a vertical axis. In some embodiments, the processing unit 4106 isfurther configured to: detect (e.g., using detecting unit 4108) acontact on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 4104), and in response to detecting the contact: enablesubstitution (e.g., with substitution enabling unit 4118), on thedisplay unit (e.g., display unit 4102), of the second user interfaceobject or the third user interface object with a display, on the displayunit (e.g., display unit 4102), of a fourth user interface object,wherein the fourth user interface object is related to the second andthe third user interface objects. In some embodiments, the first userinterface object comprises a representation of a digital clock includinga numerical indication of an hour and a numerical indication of aminute. In some embodiments, the first time is a current time.

The operations described above with reference to FIG. 26 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.41. For example, detecting operation 4102, displaying operation 4104,and animating operation 4106 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 42 shows an exemplaryfunctional block diagram of an electronic device 4200 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4200 are configured to perform the techniques described above.The functional blocks of the device 4200 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 42 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 42, an electronic device 4200 includes a display unit4202 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4204 configured to receive contacts,optionally, a movement detection unit 4220 configured to detectmovement, and a processing unit 4206 coupled to the display unit 4202,optionally, the touch-sensitive surface unit 4204 and optionally, themovement detection unit 4220. In some embodiments, the processing unit4206 includes a detecting unit 4208, a display enabling unit 4210, alaunching unit 4212, an update enabling unit 4214, a receiving unit4216, and a generating unit 4218.

The processing unit 4206 is configured to detect, by the movementdetection unit (e.g., movement detection unit 4220), a user movement ofthe electronic device 4200; and, in response to detecting the movement:enable display (e.g., with display enabling unit 4210), on the displayunit (e.g., display unit 4202), of an animated reveal of a clock face,wherein the animation comprises: enabling display (e.g., with displayenabling unit 4210), on the display unit (e.g., display unit 4202), ofan hour hand and a minute hand; and enabling display (e.g., with displayenabling unit 4210), on the display unit (e.g., display unit 4202), of afirst hour indication; and after displaying the first hour indication,enabling display (e.g., with display enabling unit 4210), on the displayunit (e.g., display unit 4202), of a second hour indication, wherein thesecond hour indication is displayed on the clock face at a positionafter the first hour indication in a clockwise direction.

In some embodiments, the processing unit 4206 is further configured to:after enabling display (e.g., with display enabling unit 4210), on thedisplay unit (e.g., display unit 4202), of the second hour indication,enable display (e.g., with display enabling unit 4210), on the displayunit (e.g., display unit 4202), of a first minute indication; and enabledisplay (e.g., with display enabling unit 4210), on the display unit(e.g., display unit 4202), of a second minute indication, wherein thesecond minute indication is displayed on the clock face at a positionafter the first minute indication in a clockwise direction. In someembodiments, the hour hand and the minute hand are displayed before thefirst hour indication. In some embodiments, the processing unit 4206 isfurther configured to: enable display (e.g., with display enabling unit4210), on the display unit (e.g., display unit 4202), of an animatedreveal of an outline of the clock face, wherein the outline of the clockface is animated to be displayed progressively in a clockwise direction.In some embodiments, after the animation, the clock face indicates acurrent time. In some embodiments, the processing unit 4206 is furtherconfigured to: enable display (e.g., with display enabling unit 4210),on the display unit (e.g., display unit 4202), of an affordance as acomplication on the clock face, wherein the affordance represents anapplication; detect (e.g., with detecting unit 4208) a contact on theaffordance on the touch-sensitive surface unit touch-sensitive surfaceunit 4204), and in response to detecting the contact: launch (e.g., withlaunching unit 4212) the application represented by the affordance. Insome embodiments, the processing unit 4206 is further configured to:enable update (e.g., with update enabling unit 4214), on the displayunit (e.g., display unit 4202), of a color of the clock face, whereinupdating the color comprises continuously changing the color of theclock face over time. In some embodiments, the color of the clock faceis a background color of the clock face. In some embodiments, the clockface comprises a seconds hand, and the color of the clock face is acolor of a seconds hand. In some embodiments, the processing unit 4206is further configured to: detect (e.g., with detecting unit 4208), bythe movement detection unit (e.g., movement detection unit 4220), asecond user movement of the electronic device 4200; and, in response todetecting the second movement: enable display (e.g., with displayenabling unit 4210), on the display unit (e.g., display unit 4202), of asecond color of the clock face, wherein the second color is differentfrom the first color; and enable update (e.g., with update enabling unit4214), on the display unit (e.g., display unit 4202), of the secondcolor of the clock face, wherein updating the second color comprisescontinuously changing the second color of the clock face over time. Insome embodiments, the processing unit 4206 is further configured to:receive (e.g., with receiving unit 4216) data representing a name; andin response to receiving the data: generate (e.g., with generating unit4218) a monogram; and enable display (e.g., with display enabling unit4210), on the display unit (e.g., display unit 4202), of the monogram asa second affordance on the clock face.

The operations described above with reference to FIG. 27A are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.42. For example, detecting operation 2702 and displaying operation 2704may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 43 shows an exemplaryfunctional block diagram of an electronic device 4300 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4300 are configured to perform the techniques described above.The functional blocks of the device 4300 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 43 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 43, an electronic device 4300 includes a display unit4302 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4304 configured to receive contacts, and aprocessing unit 4306 coupled to the display unit 4302, and optionally,the touch-sensitive surface unit 4304. In some embodiments, theprocessing unit 4306 includes a detecting unit 4308, a display enablingunit 4310, a launching unit 4312, and an updating unit 4314.

The processing unit 4306 is configured to enable display (e.g., withdisplay enabling unit), on the display unit (e.g., display unit 4302),of a user interface screen, the user interface screen including: a clockface; and an affordance, wherein the affordance represents anapplication, wherein the affordance comprises a set of informationobtained from the application, wherein the set of information is updated(e.g., with updating unit 4314) in accordance with data from theapplication, and wherein the affordance is displayed as a complicationon the clock face; detect (e.g., with detecting unit 4308) a contact onthe displayed affordance on the touch-sensitive surface unit (e.g.,touch-sensitive surface 4304), and in response to detecting the contact:launch (e.g., with launching unit 4312) the application represented bythe affordance.

The operations described above with reference to FIG. 32 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.43. For example, displaying operation 3202, detecting operation 3204,and launching operation 3206 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 44 shows an exemplaryfunctional block diagram of an electronic device 4400 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4400 are configured to perform the techniques described above.The functional blocks of the device 4400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 44 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 44, an electronic device 4400 includes a display unit4402 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4404 configured to receive contacts and todetect intensity of contacts, optionally, a rotatable input unit 4442configured to receive rotatable input (e.g., from a rotatable inputmechanism), optionally, a rotatable and depressible input unit 4444configured to receive rotatable and depressible input (e.g., from arotatable and depressible input mechanism), and a processing unit 4206coupled to the display unit 4202, optionally, the touch-sensitivesurface unit 4204, optionally, the rotatable input unit 4442, andoptionally, the rotatable and depressible input unit 4444. In someembodiments, the processing unit 4406 includes a detecting unit 4408, adisplay enabling unit 4410, a determining unit 4412, an entering unit4414, a visual distinguishment enabling unit 4416, a visual indicationenabling unit 4418, a launching unit 4420, an animation enabling unit4422, a changing unit 4424, an editing unit 4426, an obtaining unit4428, a removal enabling unit 4430, a translation enabling unit 4432, anexiting unit 4438, a reduction enabling unit 4434, an increase enablingunit 4436, a selecting unit 4440, an update enabling unit 4446, and areceiving unit 4448.

The processing unit 4406 is configured to enable display (e.g., withdisplay enabling unit 4410), on the display unit (e.g., 4402), of a userinterface screen including a clock face; detect (e.g., with detectingunit 4408) a contact on the touch-sensitive surface unit (e.g., 4404),the contact having a characteristic intensity, and in response todetecting the contact: determine (e.g., with determining unit 4412)whether the characteristic intensity is above an intensity threshold;and in accordance with a determination that the characteristic intensityis above the intensity threshold: enter (e.g., with entering unit 4414)a clock face edit mode of the electronic device; enable visualdistinguishment (e.g., with visual distinguishment enabling unit 4416,on the display unit (e.g., display unit 4402), of the displayed clockface to indicate the clock face edit mode; and detect (e.g., withdetecting unit 4408) a second contact on the touch-sensitive surfaceunit, wherein the second contact is on the visually distinguisheddisplayed clock face, and in response to detecting the second contact:enable visual indication (e.g., with visual indication enabling unit4418), on the display unit (e.g., display unit 4402), of an element ofthe clock face for editing.

In some embodiments, the clock face includes an affordance representingan application, wherein the contact is on the affordance representingthe application on the touch-sensitive surface unit, and wherein theprocessing unit 4406 is further configured to: in accordance with adetermination that the characteristic intensity is not above theintensity threshold: launch (e.g., with launching unit 4420) theapplication represented by the affordance. In some embodiments, enablingvisual distinguishment (e.g., with visual distinguishment enabling unit4416), on the display unit (e.g., display unit 4402), of the displayedclock face comprises reducing size of the displayed clock face. In someembodiments, enabling visual indication (e.g., with visual indicationenabling unit 4418), on the display unit (e.g., display unit 4402), ofthe element of the clock face for editing comprises: enabling visualdistinguishment enabling unit 4416), on the display unit (e.g., displayunit 4402), of an outline around the element of the clock face. In someembodiments, the processing unit 4406 is further configured to: enableanimation (e.g., with animation enabling unit 4422), on the display unit(e.g., 4402), of the outline around the element of the clock face todepict a rhythmic expansion and contraction of the outline. In someembodiments, visually indicating the element of the clock face forediting comprises: enabling animation (e.g., with animation enablingunit 4422), on the display unit (e.g., 4402), of the element of theclock face to depict a rhythmic expansion and contraction of the elementof the clock face. In some embodiments, visually indicating the elementof the clock face for editing comprises: enabling animation (e.g., withanimation enabling unit 4422), on the display unit (e.g., 4402), of theelement of the clock face to depict a flashing of the element of theclock face. In some embodiments, the processing unit 4406 is furtherconfigured to enable change (e.g., with changing unit 4424), on thedisplay unit (e.g., 4402), of a color of the element of the clock face,and wherein visually indicating the element of the clock face forediting comprises: changing the color of the element of the clock face.In some embodiments, the electronic device further comprises a rotatableinput unit (e.g., rotatable input unit 4442), wherein the processingunit 4406 is coupled to the rotatable input unit, and wherein theprocessing unit 4406 is further configured to: after entering the clockface edit mode: detect (e.g., with detecting unit 4408) a movementcorresponding to a rotatable input from the rotatable input unit (e.g.,rotatable input unit 4442), and in response to detecting the movement:edit (e.g., with editing unit 4426) an aspect of the visually indicatedelement of the clock face. In some embodiments, the processing unit 4406is further configured to enable change (e.g., with changing unit 4424),on the display unit (e.g., 4402), of a color of the visually indicatedelement of the clock face, and wherein editing the aspect of thevisually indicated element of the clock face comprises: enabling change(e.g., with changing unit 4424), on the display unit (e.g., display unit4402), of the color of the visually indicated element of the clock face.In some embodiments, the processing unit 4406 is further configured toenable change (e.g., with changing unit 4424), on the display unit(e.g., 4402), of a color of the visually indicated element of the clockface, wherein the visually indicated element of the clock face is aclock face background, and wherein editing (e.g., with editing unit4426) the aspect of the visually indicated element of the clock facecomprises: enabling change (e.g., with changing unit 4424), on thedisplay unit (e.g., display unit 4402), of a color of the clock facebackground. In some embodiments, the processing unit 4406 is furtherconfigured to enable change (e.g., with changing unit 4424), on thedisplay unit (e.g., 4402), of a color of the visually indicated elementof the clock face, wherein the clock face comprises a seconds hand, andwherein editing (e.g., with editing unit 4426) the aspect of thevisually indicated element of the clock face comprises: enabling change(e.g., with changing unit 4424), on the display unit (e.g., display unit4402) of a color of the seconds hand. In some embodiments, the clockface comprises an affordance representing an application, wherein theaffordance is displayed, on the display unit (e.g., display unit 4402),as a complication on the clock face, wherein the affordance indicates afirst set of information obtained from the application, and whereinediting (e.g., with changing unit 4424) the aspect of the visuallyindicated element of the clock face comprises enabling update (e.g.,with updating unit 4446), on the display unit (e.g., display unit 4402),of the affordance to indicate a second set of information obtained fromthe application. In some embodiments, the clock face comprises anaffordance representing an application, wherein the affordance isdisplayed as a complication on the clock face on the display unit,wherein the affordance indicates a set of information obtained from afirst application, wherein editing the aspect of the visually indicatedelement of the clock face comprises enabling update (e.g., with updatingunit 4446), on the display unit (e.g., display unit 4402), of theaffordance to indicate a set of information obtained from a secondapplication, and wherein the first and the second applications aredifferent. In some embodiments, the clock face comprises a plurality ofvisible divisions of time, wherein the plurality comprises a firstnumber of visible divisions of time, and wherein editing the aspect ofthe visually indicated element of the clock face comprises enablingchange (e.g., with changing unit 4424), on the display unit, of thefirst number of visible divisions of time in the plurality to a secondnumber of visible divisions of time in the plurality. In someembodiments, the second number is greater than the first number. In someembodiments, the second number is less than the first number. In someembodiments, the processing unit 4406 is further configured to: afterentering the clock face edit mode: enable display (e.g., with displayenabling unit 4410), on the display unit (e.g., 4402), of an indicatorof position along a series of positions, the indicator indicating afirst position along the series; and in response to receiving the dataindicating the rotatable input of the rotatable input unit (e.g.,rotatable input unit 4442): enable update (e.g., with update enablingunit 4446), on the display unit (e.g., display unit 4402), of theindicator of position to indicate a second position along the series. Insome embodiments, the indicator of position along a series of positionsindicates a position of a currently selected option for the editableaspect along a series of selectable options for the editable aspect ofthe visually indicated element of the clock face. In some embodiments,the indicator is displayed on the display at a position adjacent to therotatable input unit. In some embodiments, the editable aspect of thevisually indicated element of the clock face is color, and wherein theindicator comprises a series of colors, wherein each position in theseries depicts a color, and wherein the color of the currently indicatedposition along the series is representative of the color of the visuallyindicated element. In some embodiments, the processing unit 4406 isfurther configured to: after visually indicating the element of theclock face for editing: detect (e.g., with detecting unit 4408) a thirdcontact on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 4404) at a second displayed element of the clock face, andin response to detecting the third contact: enable removal (e.g., withremoval enabling unit 4430), on the display unit (e.g., display unit4402), of the visual indication of the first element of the clock facefor editing; and enable visual indication (e.g., with visual indicationenabling unit 4418), on the display unit (e.g., display unit 4402), ofthe second element of the clock face for editing. In some embodiments,before detecting the third contact, the indicated first element of theclock face is indicated by an outline around the element, whereinenabling removal (e.g., with removal enabling unit 4430) of the visualindication of the first element comprises: enabling translation (e.g.,with translation enabling unit 4432), on the display unit (e.g., displayunit 4402), of the outline on-screen away from the first element. Insome embodiments, enabling visual indication (e.g., with visualindication enabling unit 4418), on the display unit (e.g., display unit4402), of the second element of the clock face for editing comprises:enabling translation (e.g., with translation enabling unit 4432), on thedisplay unit (e.g., display unit 4402), of a visible outline on-screentowards from the second element; and enabling display (e.g., withdisplay enabling unit 4410), on the display unit (e.g., 4402), of thevisible outline around the second element, wherein the translating andthe displaying comprise a continuous on-screen movement of the visibleoutline. In some embodiments, the processing unit 4406 is furtherconfigured to: after enabling visual indication (e.g., with visualindication enabling unit 4418), on the display (e.g., display unit4402), of the first element of the clock face for editing, detect aswipe on the touch-sensitive surface unit, and in response to detectingthe swipe: enable removal (e.g., with removal enabling unit 4430), onthe display unit (e.g., display unit 4402), of the visual indication ofthe first element of the clock face for editing; enable visualindication (e.g., with visual indication enabling unit 4418), on thedisplay unit (e.g., display unit 4402), of a second element of the clockface for editing; after visually indicating the second element of theclock face for editing, detect a user input, and in response todetecting the user input: edit (e.g., with editing unit 4426) a secondaspect of the visually indicated second element of the clock face,wherein the second aspect of the second element is different from thefirst aspect of the first element of the clock face. In someembodiments, the processing unit 4406 is further configured to: enabledisplay (e.g., with display enabling unit 4410), on the display unit(e.g., 4402), of a paging affordance on the user interface screen,wherein the paging affordance indicates an editable aspect of thecurrently indicated element of the clock face, a position of theeditable aspect of the currently indicated element within a sequence ofeditable aspects, and a total number of editable aspects within thesequence of editable aspects. In some embodiments, the processing unit4406 is further configured to: after entering the clock face edit modeof the electronic device: detect (e.g., with detecting unit 4408) afourth contact on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4404), the fourth contact having a secondcharacteristic intensity, and in response to detecting the fourthcontact; determine (e.g., with determining unit 4412) whether the secondcharacteristic intensity is above a second intensity threshold; and inaccordance with a determination that the second characteristic intensityis above the second intensity threshold: exit (e.g., with exiting unit4438) the clock face edit mode; and enable cessation, on the displayunit (e.g., display unit 4402), of the visual distinguishment (e.g.,enabling the cessation of the visual distinguishment with visualdistinguishment unit 4416), on the display unit (e.g., display unit4402), of the displayed clock face. In some embodiments, enabling visualdistinguishment (e.g., with visual distinguishment unit 4416), on thedisplay unit (e.g., display unit 4402), of the displayed clock face toindicate the clock face edit mode further comprises reducing a size ofthe displayed clock face, and wherein enabling cessation, on the displayunit, of the visual distinguishment of the displayed clock facecomprises enabling an increase (e.g., with increase enabling unit 4436),on the display unit (e.g., display unit 4402), of the size of thedisplayed clock face. In some embodiments, the electronic device furthercomprises a rotatable and depressible input unit (e.g., rotatable anddepressible input unit 4444), wherein the processing unit 4406 iscoupled to the rotatable and depressible input unit, and wherein theprocessing unit 4406 is further configured to: after entering the clockface edit mode of the electronic device: detect (e.g., with detectingunit 4408) a depression corresponding to a rotatable and depressibleinput from the rotatable and depressible input unit (e.g., rotatable anddepressible input unit 4444), and in response to detecting thedepression: exit (e.g., with exiting unit 4438) the clock face editmode; and enable cessation, on the display unit, of the visualdistinguishment (e.g., enabling the cessation of the visualdistinguishment with visual distinguishment unit 4416), on the displayunit (e.g., display unit 4402), of the displayed clock face. In someembodiments, enabling visual distinguishment, on the display unit, ofthe displayed clock face to indicate the clock face edit mode comprises:enabling a reduction (e.g., with reduction enabling unit 4434), on thedisplay unit (e.g., display unit 4402), of a size of the displayed clockface, and wherein enabling cessation, on the display unit, of the visualdistinguishment (e.g., enabling the cessation of the visualdistinguishment with visual distinguishment unit 4416), on the displayunit (e.g., display unit 4402), of the displayed clock face comprises:enabling an increase (e.g., with increase enabling unit 4436), on thedisplay unit (e.g., display unit 4402), of the size of the displayedclock face. In some embodiments, the processing unit 4406 is furtherconfigured to: receive (e.g., with receiving unit 4448) a user input,and in response to receiving the user input: enter (e.g., with enteringunit 4414) a color selection mode of the electronic device 4400; whilein the color selection mode of the electronic device 4400, receive(e.g., with receiving unit 4448) data representing an image, and inresponse to receiving the data: select (e.g., with selecting unit 4440)a color of the image; and enable update (e.g., with update enabling unit4446), on the display unit (e.g., display unit 4402), of the displayedclock face, wherein enabling update the displayed clock face comprisesenabling change (e.g., with changing unit 4424), on the display unit(e.g., 4402), of a color of the clock face to the color of the image. Insome embodiments, selecting the color of the image comprises selecting acolor with greatest prevalence in the image.

The operations described above with reference to FIG. 28 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.44. For example, displaying operation 2802, detecting operation 2804,and determining operation 2806 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 45 shows an exemplaryfunctional block diagram of an electronic device 4500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4500 are configured to perform the techniques described above.The functional blocks of the device 4500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 45 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 45, an electronic device 4500 includes a display unit4502 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4504 configured to receive contacts and todetect intensity of contacts, and a processing unit 4506 coupled to thedisplay unit 4502, and optionally, the touch-sensitive surface unit4504. In some embodiments, the processing unit 4506 includes a detectingunit 4508, a display enabling unit 4510, a determining unit 4512, anentering unit 4514, a visual distinguishment enabling unit 4516, acentering enabling unit 4518, a launching unit 4520, a reductionenabling unit 4522, a translation enabling unit 4524, a simulationenabling unit 4526, an exiting unit 4528, a generating unit 4530, and ananimation enabling unit 4532.

The processing unit 4506 is configured to enable display, on the displayunit, on the touch-sensitive surface unit (e.g., touch-sensitive surfaceunit 4504) a user interface screen including a clock face; enabledisplay (e.g., with display enabling unit 4510), on the display unit(e.g., display unit 4502), on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504) (e.g., touch-sensitive surface unit4504) a user interface screen including a clock face; detect a contacton the touch-sensitive surface unit (e.g., touch-sensitive surface unit4504), the contact having a characteristic intensity, and in response todetecting the contact: determine (e.g., with determining unit 4512)whether the characteristic intensity is above an intensity threshold;and in accordance with a determination that the characteristic intensityis above the intensity threshold: enter (e.g., with entering unit 4514)a clock face selection mode of the electronic device; enable visualdistinguishment (e.g., with visual distinguishment enabling unit 4516),on the display unit (e.g., display unit 4502), of the displayed clockface to indicate the clock face selection mode, wherein the displayedclock face is centered on the display; and detect (e.g., with detectingunit 4508) a swipe on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504), and in response to detecting theswipe: enable centering (e.g., with centering enabling unit 4518), onthe display unit (e.g., display unit 4502), of a second clock face.

In some embodiments, the clock face includes an affordance representingan application, wherein the contact is on the affordance representingthe application on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504), and the processing unit is furtherconfigured to: in accordance with a determination that thecharacteristic intensity is not above the intensity threshold: launch(e.g., with launching unit 4520) the application represented by theaffordance. In some embodiments, visually distinguishing the displayedclock face to indicate the clock face selection mode comprises enablingreduction (e.g., with reduction enabling unit 4522), on the display unit(e.g., display unit 4502), of the size of the displayed clock face. Insome embodiments, the first and the second clock faces are among aplurality of clock faces, the plurality including at least the first andthe second clock face. In some embodiments, entering the clock faceselection mode of the electronic device further comprises: enablingdisplay (e.g., with display enabling unit 4510), on the display unit(e.g., display unit 4502), of at least the first and the second clockfaces from the plurality of clock faces, wherein the displayed clockfaces are shown at a reduced size and arranged in a sequence of clockfaces, and wherein the clock faces in the sequence that are notcurrently centered are displayed in a partial view. In some embodiments,the second clock face is arranged after the first clock face in thesequence of clock faces, wherein enabling centering (e.g., withcentering enabling unit 4518), on the display unit (e.g., display unit4502), of the second clock face comprises: enabling translation (e.g.,with translation enabling unit 4524), on the display unit (e.g., displayunit 4502), of the first clock face on-screen; and enabling display(e.g., with display enabling unit 4510), on the display unit (e.g.,display unit 4502), of a partial view of the first clock face. In someembodiments, centering the second clock face on the display comprises:enabling translation (e.g., with translation enabling unit 4524), on thedisplay unit (e.g., display unit 4502), of the second clock face ontothe displayed user interface screen; and enabling translation (e.g.,with translation enabling unit 4524), on the display unit (e.g., displayunit 4502), of the first clock face off of the displayed user interfacescreen. In some embodiments, enabling centering (e.g., with centeringenabling unit 4518), on the display unit (e.g., display unit 4502), ofthe second clock face on the display comprises enabling simulation(e.g., with simulation enabling unit 4526), on the display unit (e.g.,display unit 4502), of a movement of the second clock face towards theuser on the display. In some embodiments, the processing unit is furtherconfigured to: after centering the second clock face on the display:detect (e.g., with detecting unit 4508) a contact on the displayedsecond clock face on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504), and in response to detecting thecontact: exit (e.g., with exiting unit 4528) the clock face selectionmode; and enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of a second user interfacescreen including the second clock face. In some embodiments, theprocessing unit is further configured to: after entering the clock faceselection mode: detect (e.g., with detecting unit 4508) a second swipeon the touch-sensitive surface unit (e.g., touch-sensitive surface unit4504), and in response to detecting the second swipe: enable centering(e.g., with centering enabling unit 4518), on the display unit (e.g.,display unit 4502), of a clock face generation affordance on thedisplay; detect (e.g., with detecting unit 4508) a contact on thedisplayed clock face generation affordance, and in response to detectingthe contact: generate (e.g., with generating unit 4530) a third clockface; and enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of the third clock face, whereinthe third clock face is centered on the display. In some embodiments,the processing unit is further configured to: after entering the clockface selection mode, and before detecting the second swipe: enabledisplay (e.g., with display enabling unit 4510), on the display unit(e.g., display unit 4502), of at least a partial view of the clock facegeneration affordance on the user interface screen. In some embodiments,the processing unit is further configured to: after entering the clockface selection mode: detect (e.g., with detecting unit 4508) a thirdswipe on the touch-sensitive surface unit (e.g., touch-sensitive surfaceunit 4504), and in response to detecting the third swipe: enablecentering (e.g., with centering enabling unit 4518), on the display unit(e.g., display unit 4502), of a random clock face generation affordanceon the display; detect (e.g., with detecting unit 4508) a contact on thedisplayed random clock face generation affordance on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 4504), and in responseto detecting the contact: generate (e.g., with generating unit 4530) afourth clock face, wherein the fourth clock face is randomly generated;and enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of the fourth clock face,wherein the fourth clock face is centered on the display. In someembodiments, the fourth clock face is different from the first clockface, the second clock face, and the third clock face. In someembodiments, the processing unit is further configured to: afterentering the clock face selection mode, and before detecting the thirdswipe: enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of at least a partial view ofthe random clock face generation affordance on the user interfacescreen. In some embodiments, enabling centering (e.g., with centeringenabling unit 4518), on the display unit (e.g., display unit 4502), ofthe first clock face, the second clock face, the third clock face, orthe fourth clock face further comprises: enabling visibledistinguishment (e.g., with visual distinguishment enabling unit 4516),on the display unit (e.g., display unit 4502) of an outline around thecentered clock face. In some embodiments, the processing unit is furtherconfigured to: enable animation (e.g., with animation enabling unit4532), on the display unit (e.g., display unit 4502), of the outlinearound the centered clock face to depict a rhythmic expansion andcontraction of the outline. In some embodiments, enabling centering(e.g., with centering enabling unit 4518), on the display unit (e.g.,display unit 4502), of the first clock face, the second clock face, thethird clock face, or the fourth clock face further comprises: enablinganimation (e.g., with animation enabling unit 4532), on the display unit(e.g., display unit 4502), of the centered clock face to depict arhythmic expansion and contraction of the centered clock face. In someembodiments, enabling centering (e.g., with centering enabling unit4518), on the display unit (e.g., display unit 4502), of the first clockface, the second clock face, the third clock face, or the fourth clockface further comprises: enabling animation (e.g., with animationenabling unit 4532), on the display unit (e.g., display unit 4502), ofthe centered clock face to depict a flashing of the centered clock face.In some embodiments, the processing unit is further configured to:enable display (e.g., with display enabling unit 4510), on the displayunit (e.g., display unit 4502), of a paging affordance on the userinterface screen, wherein the paging affordance indicates the currentlycentered clock face, a position of the centered clock face within asequence of clock faces, and a total number of clock faces within thesequence of clock faces.

The operations described above with reference to FIGS. 29-30 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.45. For example, displaying operation 2902, detecting operation 2904,and determining operation 2906 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 46 shows an exemplaryfunctional block diagram of an electronic device 4600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4600 are configured to perform the techniques described above.The functional blocks of the device 4600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 46 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 46, an electronic device 4600 includes a display unit4602 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4604 configured to receive contacts,optionally, a rotatable input unit 4618 configured to receive rotatableinput (e.g., from a rotatable input mechanism), optionally, an audiounit 4620 configured to generate audio, optionally, a haptic unit 4622configured to generate haptic output, and a processing unit 4606 coupledto the display unit 4502, optionally, the touch-sensitive surface unit4504, optionally, the rotatable input unit 4618, optionally, the audiounit 4620, and optionally, the haptic unit 4622. In some embodiments,the processing unit 4606 includes a detecting unit 4608, a displayenabling unit 4610, an entering unit 4612, an update enabling unit 4614,and a setting unit 4616.

The processing unit 4606 is configured to enable display (e.g., withdisplay enabling unit 4610), on the display unit (e.g., display unit4602), of a user interface screen, the user interface screen including:a clock face; and an affordance on the clock face, the affordanceindicating a first time of day; detect (e.g., with detecting unit 4608)a contact on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 4604); and in response to detecting the contact: enter(e.g., with entering unit 4612) a user interaction mode of theelectronic device; while the electronic device is in the userinteraction mode, detect (e.g., with detecting unit 4608) a rotatableinput from the rotatable input unit (e.g., rotatable input unit 4618),and in response to detecting the rotatable input: enable update (e.g.,with update enabling unit 4614), on the display unit (e.g., display unit4602), of the affordance to indicate a second time of day; detect (e.g.,with detecting unit 4608) a second contact on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 4604) at the affordanceindicating the second time, and in response to detecting the secondcontact: set (e.g., with setting unit 4616) a user reminder for thesecond time of day.

In some embodiments, setting the user reminder for the second time ofday comprises: enabling display (e.g., with display enabling unit 4610),on the display unit (e.g., display unit 4602), of a second affordance onthe display, the second affordance representing a user prompt to set analert for the second time of day. In some embodiments, the processingunit is further configured to enable display (e.g., with displayenabling unit 4610), on the display unit (e.g., display unit 4602), of avisual alert for the second time of day, and wherein the user reminderfor the third time of day comprises the visual alert for the second timeof day. In some embodiments, the electronic device 4600 furthercomprises an audio unit (e.g., audio unit 4620), wherein the processingunit is coupled to the audio unit, and wherein the processing unit isfurther configured to enable an audio alert for the second time of dayvia the audio unit (e.g., with audio unit 4620), and wherein the userreminder for the third time of day comprises the audio alert for thesecond time of day. In some embodiments, the electronic device 4600further comprises a haptic unit (e.g., haptic unit 4622), wherein theprocessing unit is coupled to the haptic unit, and wherein theprocessing unit is further configured to enable a haptic alert for thesecond time of day via the haptic unit (e.g., with haptic unit 4622),and wherein the user reminder for the second time of day comprises thehaptic alert for the second time of day.

The operations described above with reference to FIG. 31 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.46. For example, displaying operation 3102, detecting operation 3104,and entering operation 3106 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 47 shows an exemplaryfunctional block diagram of an electronic device 4700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4700 are configured to perform the techniques described above.The functional blocks of the device 4700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 47 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 47, an electronic device 4700 includes a display unit4702 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4704 configured to receive contacts,optionally, an audio unit 4738 configured to generate audio, optionally,a haptic unit 4740 configured to generate haptic output, optionally, alocation sensing unit 4742 configured to sense location, optionally, amovement detection unit 4744, and a processing unit 4706 coupled to thedisplay unit 4702, optionally, the touch-sensitive surface unit 4704,optionally, the audio unit 4738, optionally, the haptic unit 4740,optionally, the location sensing unit 4742, and optionally, the movementdetection unit 4744. In some embodiments, the processing unit 4706includes a detecting unit 4708, a display enabling unit 4710, asubstitution enabling unit 4712, an animation enabling unit 4714, areceiving enabling unit 4716, a determining unit 4718, a removalenabling unit 4720, a launching unit 4722, an accessing unit 4724, anobtaining unit 4726, an update enabling unit 4728, a moving enablingunit 4730, a starting unit 4732, a stopping unit 4734, and a providingunit 4736.

The processing unit 4706 is configured to enable display (e.g., withdisplay enabling unit 4710), on the display unit (e.g., display unit4702), of a user interface screen, the user interface screen including aplurality of affordances, the plurality including a first affordance,wherein the first affordance indicates a clock face that includes: anindication of time; and an outline; detect (e.g., with detecting unit4708) a contact on the displayed first affordance on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 4704); and in responseto detecting the contact: enable substitution (e.g., with substitutionenabling unit 4712), on the display unit (e.g., display unit 4702), ofthe user interface screen with a second user interface screen, whereinthe substitution comprises retaining one of the one or more of theindication of time and the outline, wherein the retained indication oftime or outline is displayed on the second user interface screen at asize larger than on the first user interface screen.

In some embodiments, the processing unit 4706 is further configured to:enable animation (e.g., with animation enabling unit 4714), on thedisplay unit (e.g., display unit 4702), of the one or more retainedelements by progressively displaying the element on the second userinterface screen. In some embodiments, the outline is retained, andwherein the outline is progressively displayed in a rotational motion.

In some embodiments, the processing unit 4706 is further configured to:receive (e.g., with receiving unit 4716) a notification; determine(e.g., with determining unit 4718) whether the notification has beenmissed; and in accordance with a determination that notification hasbeen missed: enable display (e.g., with display enabling unit 4710), onthe display unit (e.g., display unit 4702), of an affordance, theaffordance indicating a missed notification. In some embodiments, anaspect of the displayed affordance represents a number of missednotifications received by the electronic device. In some embodiments,the processing unit 4706 is further configured to: receive datarepresenting user viewing of the missed notification, and in response toreceiving the data: enable removal (e.g., with removal enabling unit4720), on the display unit (e.g., display unit 4702), of the affordance.In some embodiments, the processing unit 4706 is further configured to:enable display (e.g., with display enabling unit 4710), on the displayunit (e.g., display unit 4702), of a stopwatch progress affordance, thestopwatch progress affordance indicating a currently running stopwatchapplication, wherein the stopwatch progress affordance comprises arepresentation of a digital stopwatch, and wherein the representation ofthe digital stopwatch is continuously updated (e.g., with updateenabling unit 4728) to indicate a stopwatch time generated by thecurrently running stopwatch application; detect (e.g., with detectingunit 4708) a contact on the displayed stopwatch progress affordance, andin response to detecting the contact: launch (e.g., with launching unit4722) the stopwatch application. In some embodiments, the electronicdevice comprises a location sensing unit (e.g., location sensing unit4742), wherein the processing unit 4706 is coupled to the locationsensing unit, and the processing unit 4706 is further configured to:while a clock face is displayed on the display unit, detect (e.g., withdetecting unit 4708) a contact on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 4704), and in response to detectingthe contact: access (e.g., with accessing unit 4724) data representing adesignated home location, the designated home location having anassociated home time zone; obtain (e.g., with obtaining unit 4726) acurrent time zone of the electronic device from the location sensor;determine (e.g., with determining unit 4718) whether the current timezone is different from the home time zone; and in response to adetermination that the current time zone is different from the home timezone: enable update (e.g., with update enabling unit 4728), on thedisplay unit (e.g., display unit 4702), of the displayed clock face toindicate a current time at the home time zone. In some embodiments, thedesignated home location is user-designated. In some embodiments, thedesignated home location is a location designated by the system based ondata representing one or more of: amount of time spent at the location;which times of day are spent at the location; and number of contactentries associated with the location stored on the electronic device. Insome embodiments, the electronic device 4700 further includes a movementdetection unit (e.g., movement detection unit 4744), the processing unit4706 is coupled to the movement detection unit, and the processing unit4706 is further configured to: enable display (e.g., with displayenabling unit 4710), on the display unit (e.g., display unit 4702), of aclock face on the display, the displayed clock face comprising aplurality of pixels; detect (e.g., with detecting unit 4708) a movementof the electronic device 4700 via the movement detection unit (e.g.,movement detection unit 4744); and in response to detecting themovement: enable moving (e.g., with moving enabling unit 4730), on thedisplay unit (e.g., display unit 4702), of the displayed clock face onthe display, wherein moving comprises modifying in appearance a subsetof pixels in the plurality. In some embodiments, the processing unit4706 is further configured to: enable display (e.g., with displayenabling unit 4710), on the display unit (e.g., display unit 4702), of atachymeter user interface object comprising a start/stop affordance;detect (e.g., with detecting unit 4708) a user input at a first time; inresponse to detecting the user input: start (e.g., with starting unit4732) a virtual tachymeter; detect (e.g., with detecting unit 4708) asecond user input at a second time, the second time separated from thefirst time by a tachymeter interval; in response to detecting the seconduser input: stop (e.g., with stopping unit 4734) the virtual tachymeter;and enable display (e.g., with display enabling unit 4710), on thedisplay unit (e.g., display unit 4702), of a time value based on anumber of units of time in a predetermined interval divided by thetachymeter interval. In some embodiments, the processing unit 4706 isfurther configured to: enable display (e.g., with display enabling unit4710), on the display unit (e.g., display unit 4702), of a telemeteruser interface object comprising a start/stop affordance; detect (e.g.,with detecting unit 4708) a user input at a first time; in response todetecting the user input: start (e.g., with starting unit 4732) avirtual telemeter; detect (e.g., with detecting unit 4708) a second userinput at a second time, the second time separated from the first time bya telemeter interval; in response to detecting the second contact: stop(e.g., with stopping unit 4734) the virtual telemeter; and enabledisplay (e.g., with display enabling unit 4710), on the display unit(e.g., display unit 4702), of a distance based on the telemeterinterval. In some embodiments, the processing unit 4706 is furtherconfigured to: enable display (e.g., with display enabling unit 4710),on the display unit (e.g., display unit 4702), of a repeated intervaltimer user interface; receive (e.g., with receiving unit 4716) datarepresenting a user-designated time interval; and in response toreceiving the data representing the user-designated time interval:provide (e.g., with providing unit 4736) a user alert, wherein the useralert is repeated at times based on the user-designated time interval.In some embodiments, the user alert comprises one or more of: a visualalert, enabled on the display unit (e.g., display unit 4702); an audioalert, wherein the electronic device further comprises an audio unit(e.g., audio unit 4738) coupled to the processing unit, and wherein theprocessing unit is further configured to enable an audio alert via theaudio unit (e.g., audio unit 4738); and a haptic alert, wherein theelectronic device further comprises a haptic unit (e.g., haptic unit4740) coupled to the processing unit, and wherein the processing unit isfurther configured to enable a haptic alert via the haptic unit (e.g.,haptic unit 4738).

The operations described above with reference to FIG. 33 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.47. For example, displaying operation 3302, detecting operation 3304,and substituting operation 3306 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 48 shows an exemplaryfunctional block diagram of an electronic device 4800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4800 are configured to perform the techniques described above.The functional blocks of the device 4800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 48 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 48, an electronic device 4800 includes a display unit4802 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4804 configured to receive contacts, and aprocessing unit 4806 coupled to the display unit 4802, and optionally,the touch-sensitive surface unit 4804. In some embodiments, theprocessing unit 4806 includes an update enabling unit 4808, a displayenabling unit 4810, and an indication enabling unit 4812.

The processing unit 4806 is configured to enable display (e.g., withdisplay enabling unit 4810), on the display unit (e.g., display unit4802), of a character user interface object, the character userinterface object comprising representations of a first limb and a secondlimb, wherein the processing unit 4806 is configured to enable thecharacter user interface object to indicate (e.g., with indicationenabling unit 4812), on the display unit (e.g., display unit 4802), afirst time by: enabling indication (e.g., with indication enabling unit4812), on the display unit (e.g., display unit 4802), of a first hourwith the first limb and a first minute with the second limb; and enableupdate (e.g., with update enabling unit 4808), on the display unit(e.g., display unit 4802), of the character user interface object toindicate a second time, wherein the processing unit is configured toenable the character user interface object to indicate (e.g., withindication enabling unit 4812), on the display unit (e.g., display unit4802), the second time by: enabling indication (e.g., with indicationenabling unit 4812), on the display unit (e.g., display unit 4802), of asecond hour with the second limb and a second minute with the firstlimb.

In some embodiments, enabling update (e.g., with update enabling unit4808), on the display unit (e.g., display unit 4802), of the characteruser interface object to indicate a second time comprises enabling anextension of the first limb and a retraction of the second limb on thedisplay unit.

The operations described above with reference to FIG. 27B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.48. For example, displaying operation 2712, updating operation 2714, andthe optional updating operation within block 2714 may be implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub event, such as activation of an affordance on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 49 shows an exemplaryfunctional block diagram of an electronic device 4900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4900 are configured to perform the techniques described above.The functional blocks of the device 4900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 49 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 49, an electronic device 4900 includes a display unit4902 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4904 configured to receive contacts, and aprocessing unit 4906 coupled to the display unit 4902, and optionally,the touch-sensitive surface unit 4904. In some embodiments, theprocessing unit 4906 includes an update enabling unit 4908, a displayenabling unit 4910, and a moving enabling unit 4912.

The processing unit 4806 is configured to enable display (e.g., withdisplay enabling unit 4910), on the display unit (e.g., display unit4902), of a character user interface object on the display, thecharacter user interface object comprising a representation of a limb,the limb including: a first endpoint of the limb having a firstposition, wherein the first endpoint of the limb is an axis of rotationfor the limb, and a second endpoint of the limb having a secondposition, wherein the position of the second endpoint of the limbindicates a first time value; and enable update (e.g., with updateenabling unit 4908), on the display unit (e.g., display unit 4902), ofthe character user interface object to indicate a second time value,wherein enabling update, on the display unit, of the character userinterface object comprises enabling moving (e.g., with moving enablingunit 4912), on the display unit (e.g., display unit 4902), of the firstendpoint of the limb to a third position, and moving the second endpointof the limb to a fourth position to indicate the second time value.

In some embodiments, the character user interface object furthercomprises a representation of a second limb, the second limb including:a first endpoint of the second limb having a first position, wherein thefirst endpoint of the second limb is an axis of rotation for the secondlimb, and a second endpoint of the second limb having a second position,wherein the position of the second endpoint of the second limb indicatesa third time value, and the processing unit is further configured to:enable update (e.g., with update enabling unit 4908), on the displayunit (e.g., display unit 4902), of the character user interface objectto indicate a fourth time value, wherein enabling update, on the displayunit, of the character user interface object to indicate the fourth timevalue comprises enabling moving (e.g., with moving enabling unit 4912),on the display unit (e.g., display unit 4902), of the first endpoint ofthe second limb to a third position, and enabling moving (e.g., withmoving enabling unit 4912), on the display unit (e.g., display unit4902), of the second endpoint of the second limb to a fourth position toindicate the fourth time value.

The operations described above with reference to FIG. 27C are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.49. For example, displaying operation 2722 and updating operation 2724may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 50 shows an exemplaryfunctional block diagram of an electronic device 5000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5000 are configured to perform the techniques described above.The functional blocks of the device 5000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 50 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 50, an electronic device 5000 includes a display unit5002 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 5004 configured to receive contacts, and aprocessing unit 5006 coupled to the display unit 5002, and optionally,the touch-sensitive surface unit 5004. In some embodiments, theprocessing unit 5006 includes an update enabling unit 5008, a displayenabling unit 5010, an animation enabling unit 5012, a translationenabling unit 5014, a change enabling unit 5016, and a moving enablingunit 5018.

The processing unit 5006 is configured to enable display (e.g., withdisplay enabling unit 5010), on the display unit (e.g., display unit5002), of a character user interface object, the character userinterface object comprising a representation of a limb, the limbincluding a first segment of the limb and a second segment of the limb,wherein the first segment of the limb connects a first endpoint of thelimb to a joint of the limb, the first endpoint of the limb having afirst position, and wherein the second segment of the limb connects asecond endpoint of the limb to the joint of the limb, the secondendpoint of the limb having a second position, wherein the joint of thelimb is an axis of rotation for the second segment of the limb, andwherein the position of the second endpoint of the limb indicates afirst time value; and enable update (e.g., with update enabling unit5008), on the display unit (e.g., display unit 5002), of the characteruser interface object to indicate a second time value, wherein enablingupdate comprises enabling moving (e.g., with moving enabling unit 5018),on the display unit (e.g., display unit 5002), of the second endpoint ofthe limb along the axis of rotation for the second segment of the limbto a third position to indicate the second time.

In some embodiments, enabling update (e.g., with update enabling unit5008), on the display unit (e.g., display unit 5002), of the characteruser interface object further comprises enabling moving (e.g., withmoving enabling unit 5018), on the display unit (e.g., display unit5002), of the first endpoint. In some embodiments, the character userinterface object further comprises a representation of a second limb,the second limb including a first segment of the second limb and asecond segment of the second limb, wherein the first segment of thesecond limb connects a first endpoint of the second limb to a joint ofthe second limb, the first endpoint of the second limb having a firstposition, wherein the second segment of the second limb connects asecond endpoint of the second limb to the joint of the second limb, thesecond endpoint of the second limb having a second position, wherein thejoint of the second limb is an axis of rotation for the second segmentof the second limb, and wherein the position of the second endpoint ofthe second limb indicates a third time, and wherein the processing unit5006 is further configured to: enable update (e.g., with update enablingunit 5008), on the display unit (e.g., display unit 5002), of thecharacter user interface object to indicate a fourth time, whereinenabling update comprises enabling moving (e.g., with moving enablingunit 5018), on the display unit (e.g., display unit 5002), of the secondendpoint of the second limb along the axis of rotation for the secondsegment of the second limb to a third position to indicate the fourthtime value. In some embodiments, the first limb indicates an hour andthe second limb indicates a minute. In some embodiments, the first limbindicates a minute and the second limb indicates an hour. In someembodiments, enabling update (e.g., with update enabling unit 5008), onthe display unit (e.g., display unit 5002), of the character userinterface object to indicate the second time further comprises: enablinganimation (e.g., with animation enabling unit 5012), on the display unit(e.g., display unit 5002), of the character user interface object,wherein enabling animation, on the display unit, of the character userinterface object comprises a motion of the first endpoint on-screen. Insome embodiments, enabling update (e.g., with update enabling unit5008), on the display unit (e.g., display unit 5002), of the characteruser interface object further comprises: enabling animation (e.g., withanimation enabling unit 5012), on the display unit (e.g., display unit5002), of the character user interface object, wherein enablinganimation, on the display unit, of the character user interface objectcomprises a rotation of the second segment at the joint on-screen. Insome embodiments, the processing unit is further configured to: enabletranslation (e.g., with translation enabling unit 5014), on the displayunit (e.g., display unit 5002), of the character user interface objecton-screen towards a center of the display. In some embodiments, enablingtranslation (e.g., with translation enabling unit 5014), on the displayunit (e.g., display unit 5002), of the character user interface objectcomprises animating the character user interface object to representwalking. In some embodiments, the processing unit is further configuredto: enable change (e.g., with change enabling unit 5016), on the displayunit (e.g., display unit 5002), of a visual aspect of the display tohighlight the character user interface object. In some embodiments, theprocessing unit is further configured to: enable animation (e.g., withanimation enabling unit 5012), on the display unit (e.g., display unit5002), of the character user interface object in response to beinghighlighted. In some embodiments, the character user interface objectfurther comprises a representation of a foot. In some embodiments, theprocessing unit is further configured to: enable animation (e.g., withanimation enabling unit 5012), on the display unit (e.g., display unit5002), of the foot to indicate passage of time. In some embodiments, thefirst time and the second time are the same. In some embodiments, theprocessing unit is further configured to: enable display (e.g., withdisplay enabling unit 5010), on the display unit (e.g., display unit5002), of a numerical indication of a time value.

The operations described above with reference to FIG. 27D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.50. For example, displaying operation 2732 and updating operation 2734may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 51 shows an exemplaryfunctional block diagram of an electronic device 5100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5100 are configured to perform the techniques described above.The functional blocks of the device 5100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 51 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 51, an electronic device 5100 includes a display unit5102 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 5104 configured to receive contacts,optionally, a movement detection unit 5120 configured to detectmovement, and a processing unit 5106 coupled to the display unit 5102,optionally, the touch-sensitive surface unit 5104 and optionally, themovement detection unit 5120. In some embodiments, the processing unit5106 includes a receiving unit 5108, a display enabling unit 5110, adetermining unit 5112, an update enabling unit 5114, an animationenabling unit 5116, a detecting unit 5118, an animation enabling unit5122, and a change enabling unit 5124.

The processing unit 5106 is configured to enable display (e.g., withdisplay enabling unit 5110), on the display unit (e.g., display unit5102), of a character user interface object, wherein the character userinterface object indicates a current time; receive (e.g., with receivingunit 5108) first data indicative of an event; determine (e.g., withdetermining unit 5112) whether the event meets a condition; and inaccordance with the determination that the event meets the condition:enable update (e.g., with update enabling unit 5114), on the displayunit (e.g., display unit 5102), of the displayed character userinterface object by changing (e.g., with change enabling unit 5124) avisual aspect of the character user interface object.

In some embodiments, after enabling update (e.g., with update enablingunit 5114), on the display unit (e.g., display unit 5102), of thedisplayed character user interface object, the character user interfaceobject still indicates the current time. In some embodiments, afterenabling update (e.g., with update enabling unit 5114), on the displayunit (e.g., display unit 5102), of the displayed character userinterface object, the character user interface object no longerindicates the current time. In some embodiments, the first dataindicates a calendar event; the condition corresponds to a duration ofthe calendar event; and determining whether the event meets thecondition comprises determining whether the current time is within theduration of the calendar event. In some embodiments, the calendar eventis a birthday, and wherein enabling update (e.g., with update enablingunit 5114), on the display unit (e.g., display unit 5102), of thedisplayed character user interface object comprises enabling animation(e.g., with animation enabling unit 5122), on the display unit (e.g.,display unit 5102), of the character user interface object to display abirthday greeting. In some embodiments, the calendar event is a holiday,and wherein updating the displayed character user interface objectcomprises enabling change (e.g., with change enabling unit 5124), on thedisplay unit (e.g., display unit 5102), of a visual aspect of thecharacter user interface object to reflect the holiday. In someembodiments, the first data indicates a notification, and wherein theprocessing unit is further configured to: enable display (e.g., withdisplay enabling unit 5110), on the display unit (e.g., display unit5102), of the notification on the display; and enable animation (e.g.,with animation enabling unit 5122), on the display unit (e.g., displayunit 5102), of the character user interface object to react to thedisplayed notification. In some embodiments, the first data indicates atime of day; the condition corresponds to a nighttime portion of theday; determining whether the event meets the condition comprisesdetermining whether the time of day is within the nighttime portion ofthe day; and enabling update (e.g., with update enabling unit 5114), onthe display unit (e.g., display unit 5102), of the displayed characteruser interface object comprises enabling change (e.g., with changeenabling unit 5124), on the display unit (e.g., display unit 5102), ofthe visual aspect of the character user interface object to representnighttime. In some embodiments, the first data indicates the currenttime; the condition corresponds to an hour on the hour; determiningwhether the event meets the condition comprises determining whether thecurrent time is an hour on the hour; and enabling update (e.g., withupdate enabling unit 5114), on the display unit (e.g., display unit5102), of the displayed character user interface object comprisesenabling animation (e.g., with animation enabling unit 5122), on thedisplay unit (e.g., display unit 5102), of the character user interfaceobject to announce the hour on the hour for one or more hours. In someembodiments, the first data indicates current or forecasted weather; thecondition corresponds to one or more designated weather conditions;determining whether the event meets the condition comprises determiningwhether the current or forecasted weather is one of the one or moredesignated weather conditions; and enabling update (e.g., with updateenabling unit 5114), on the display unit (e.g., display unit 5102), ofthe displayed character user interface object comprises enabling change(e.g., with change enabling unit 5124), on the display unit (e.g.,display unit 5102), of the visual aspect of the character user interfaceobject to reflect the current or forecasted weather. In someembodiments, the first data indicates a second electronic device; thecondition corresponds to a threshold proximity to the first electronicdevice; determining whether the event meets the condition comprisesdetermining whether the second electronic device is within the thresholdproximity to the first electronic device; and enabling update (e.g.,with update enabling unit 5114), on the display unit (e.g., display unit5102), of the displayed character user interface object comprisesenabling animation (e.g., with animation enabling unit 5122), on thedisplay unit (e.g., display unit 5102), of the character user interfaceobject to react to the second electronic device. In some embodiments,the first data indicates user activity; the condition corresponds to athreshold interval after a previous user activity; determining whetherthe event meets the condition comprises determining whether the firstdata is received outside of the threshold interval after the previoususer activity; and enabling update (e.g., with update enabling unit5114), on the display unit (e.g., display unit 5102), of the displayedcharacter user interface object comprises enabling animation (e.g., withanimation enabling unit 5122), on the display unit (e.g., display unit5102), of the character user interface object to reflect inactivity. Insome embodiments, the first data indicates user activity; the conditioncorresponds to current user activity; determining whether the eventmeets the condition comprises determining whether the user activity iscurrent user activity; and updating the displayed character userinterface object comprises enabling animation (e.g., with animationenabling unit 5122), on the display unit (e.g., display unit 5102), ofthe character user interface object to represent exercise. In someembodiments, the first data indicates user movement of the device (e.g.,from movement detection unit 5120); the condition corresponds to athreshold interval after a previous user movement of the device;determining whether the event meets the condition comprises determiningwhether the first data is received outside of the threshold intervalafter the previous user movement of the device (e.g., from movementdetection unit 5120); and enabling update (e.g., with update enablingunit 5114), on the display unit (e.g., display unit 5102), of thedisplayed character user interface object comprises enabling animation(e.g., with animation enabling unit 5122), on the display unit (e.g.,display unit 5102), of the character user interface object to representfatigue. In some embodiments, the first data indicates user contact onthe touch-sensitive surface unit (e.g., touch-sensitive surface unit5104); the condition corresponds to a user contact on the displayedcharacter user interface object; determining whether the event meets thecondition comprises determining whether the user contact on thetouch-sensitive surface unit is on the displayed character userinterface object; and enabling update (e.g., with update enabling unit5114), on the display unit (e.g., display unit 5102), of the displayedcharacter user interface object comprises enabling animation (e.g., withanimation enabling unit 5122), on the display unit (e.g., display unit5102), of the character user interface object to react to the contact.In some embodiments, the processing unit 5106 is further configured to:detect (e.g., with detecting unit 5118) a user input; and in response todetecting the user input, enable display (e.g., with display enablingunit 5110), on the display unit (e.g., display unit 5102), of thecharacter user interface object. In some embodiments, the user inputcomprises a user movement of the device, wherein the electronic devicefurther comprises a movement detection unit (e.g., movement detectionunit 5120), wherein the processing unit 5106 is coupled to the movementdetection unit, and wherein the processing unit 5106 is furtherconfigured to: detect, by the movement detection unit (e.g., movementdetection unit 5120), the user movement of the device 5100. In someembodiments, the user input comprises a contact on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 5104), and wherein theprocessing unit 5106 is further configured to detect (e.g., withdetecting unit 5118) the contact on the touch-sensitive surface unit.

The operations described above with reference to FIG. 27E are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.51. For example, displaying operation 2742, receiving operation 2744,and determining operation 2746 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 52 shows an exemplaryfunctional block diagram of an electronic device 5200 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5200 are configured to perform the techniques described above.The functional blocks of the device 5200 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 52 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 52, an electronic device 5200 includes a display unit5202 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 5204 configured to receive contacts,optionally, a movement detection unit 5216 configured to detectmovement, optionally, a button input unit 5218 configured to receiveinput from a button, and a processing unit 5206 coupled to the displayunit 5202, optionally, the touch-sensitive surface unit 5204,optionally, the movement detection unit 5216, and optionally, the buttoninput unit 5218. In some embodiments, the processing unit 5206 includesa setting unit 5208, a display enabling unit 5210, an animation enablingunit 5212, and a receiving unit 5214.

The processing unit 5206 is configured to set (e.g., with setting unit5208) the display unit (e.g., display unit 5202) to an inactive state;receive (e.g., with receiving unit 5214) first data indicative of anevent; in response to receiving the first data: set (e.g., with settingunit 5208) the display unit (e.g., display unit 5202) to an activestate; enable display (e.g., with display enabling unit 5210), on thedisplay unit (e.g., display unit 5202), of a character user interfaceobject on a side of the display; enable animation (e.g., with animationenabling unit 5212), on the display unit (e.g., display unit 5202), ofthe character user interface object towards a center of the display; andenable display (e.g., with display enabling unit 5210), on the displayunit (e.g., display unit 5202), of the character user interface objectat the center of the display in a position that indicates a currenttime.

In some embodiments, enabling animation (e.g., with animation enablingunit 5212), on the display unit (e.g., display unit 5202), of thecharacter user interface object provides the impression of walking. Insome embodiments, the electronic device 5200 includes a movementdetection unit (e.g., movement detection unit 5216), wherein themovement detection unit is coupled to the processing unit 5206, and theprocessing unit 5206 is further configured to receive (e.g., withreceiving unit 5214) input from the movement detection unit, and whereinthe event includes a motion raising the electronic device 5200 into aviewing position. In some embodiments, the electronic device 5200includes a button input unit (e.g., button input unit 5218), wherein thebutton input unit is coupled to the processing unit 5206, and theprocessing unit 5206 is further configured to receive input from thebutton input unit, and wherein the event includes a press on the buttoninput unit on the device 5200. In some embodiments, the event includes atouch on the touch-sensitive surface (e.g., touch-sensitive surface unit5204).

The operations described above with reference to FIG. 27F are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.52. For example, setting operation 2752, receiving operation 2754, andsetting operation 2756 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

Attention is now directed toward embodiments of user interfaces andassociated processes that may be implemented on an electronic device,such as device 100, 300, or 500.

FIGS. 53A-53F illustrate exemplary user interfaces. FIGS. 54A-54E areflow diagrams illustrating exemplary methods. The user interfaces inFIGS. 53C-53F are used to illustrate the processes in FIGS. 54A-54E.

FIGS. 53A-53F depict device 5300, which in some embodiments includessome or all of the features described with respect to devices 100, 300,and/or 500. In some embodiments, device 5300 has touch-sensitive andpressure-sensitive display 5302 (sometimes simply called atouch-screen). In some embodiments, device 5300 has rotatable anddepressible input mechanism 5304. In some embodiments, device 5300 hasdepressible input mechanism 5306. Display 5302 and input mechanisms 5304and 5306 may share some or all characteristics, respectively, withdisplay 504 and input mechanisms 506 and 508.

In some embodiments, device 5300 includes an attachment mechanism forattaching, affixing, or connecting a device to a body part or toclothing of a user. In this manner, device 5300 may be considered a“wearable device,” sometimes simply referred to as a “wearable.” In theexamples of FIGS. 53A and 53B, device 5300 may comprise a wrist strap(not pictured), which may be used to affix the device to the wrist of auser. In some embodiments, device 5300 takes the form factor of a “smartwatch,” a portable electronic device configured to be affixed by a strapto the wrist of a user.

Attention is now directed toward techniques for accessing and presentinginformation corresponding to past times and future times. In someembodiments, a user interface is configured to present information inthe form of complications, which can optionally be visually displayeduser interface objects sharing any or all of the characteristics ofcomplications discussed above in this disclosure.

In some embodiments, a user can optionally access a “time scrubbing”mode or a “time travel” mode, and associated user interfaces. In “timescrubbing” or “time travel” mode, a user can optionally advance orrewind a non-current time, also called a “scrubbing time.” “Scrubbing”may refer to the action of progressing through time forward, orprogressing through time backward. A user may “scrub forward” as hecauses a scrubbing time to advance further into the future (as iffast-forwarding), and a user may “scrub backward” as he causes ascrubbing time to move further into the past (as if rewinding). Ratherthan corresponding to the current time of day (or to a time somewhereelse in the world), the scrubbing time can optionally be set inaccordance with a user input. As the user sets and updates the scrubbingtime (e.g., as the user scrubs), the information displayed in interfacesassociated with time-scrubbing mode can optionally be updated inaccordance with the scrubbing time. Namely, the scrubbing time canoptionally be displayed on the time scrubbing interface, and adifference between the scrubbing time and the current time canoptionally be displayed on the time scrubbing interface. In someembodiments, an indicator of the difference between the current time andthe scrubbing time is displayed. In some embodiments, one or morecomplications can optionally be updated in accordance with the scrubbingtime, such that the complications, while the device is in time-scrubbingmode, display information corresponding to the scrubbing time ratherthan information corresponding to the current time. In this way, thedevice may appear to “travel” through time as the scrubbing timeadvances into the future or rewinds into the past, and the displayedcomplications are updated accordingly. In some embodiments, thecomplications can optionally display forecasted or predicted informationcorresponding to a scrubbing time in the future, and can optionallydisplay recorded or historical information corresponding to a scrubbingtime in the past.

Features described can allow a user to use time-scrubbing mode toquickly, easily, and intuitively access past and future informationcorresponding to a plurality of displayed complications; the user mayeasily view information corresponding to more than one complication forthe same point in the future or point in the past, and may appreciatethe manner in which the information corresponding to differentcomplications did or will interrelate by virtue of corresponding to thesame scrubbing time. For example, a user can optionally scrub forward intime to see that a calendar event later in the day corresponds to aforecasted thunderstorm; information which the user may not haveappreciated if the user viewed the future event in a calendarapplication interface and the forecasted weather in a separate weatherapplication interface.

Attention is now specifically directed to interfaces for time scrubbinga likeness of an analog clock face.

FIG. 53A depicts exemplary user interface 5340, displayed on display5302 of device 5300. In some embodiments, user interface 5340 is a watchface interface screen, such as a home interface of a wearablesmart-watch portable electronic device. Interface 5340 includes watchface 5308, which is a displayed likeness of an analog watch face. Watchface 5308 includes hour hand 5310 a and minute hand 5310 b. In someembodiments, watch face 5308 can optionally further include a secondhand. In FIG. 53A, hour hand 5310 a and minute hand 5310 b indicate thatthe current time is 11:09.

Interface 5340 further includes weather complication 5312, which is acomplication configured to indicate weather data for a user-selectedlocation. In some embodiments, weather complication 5312 can optionallybe associated with a weather application from which it draws weatherdata. In some embodiments, weather complication 5312 can optionally be aselectable affordance, such that detection of a user input at a locationon display 5302 corresponding to weather complication 5312 canoptionally cause an associated interface to be displayed, additionalinformation to be displayed, or an associated application (e.g., aweather application) to be accessed or opened. In some embodiments,weather complication 5312 can optionally display information about thetemperature, the precipitation, the wind speed, the cloud cover, or anyother relevant or useful weather information.

In some embodiments, weather complication 5312 can optionally displayinformation corresponding to present information, to future information(e.g., future scheduled events, predicted/forecasted information, etc.),or to past information (e.g., historical information, recorded events,past events, past predictions/forecasts, etc.). In the depicted example,weather complication 5312 is displaying current weather information,indicating that the current air temperature is 72°.

Interface 5340 further includes stock-market complication 5314, which isa complication configured to indicate stock-market data. In someembodiments, stock-market complication 5314 can optionally be associatedwith a stock-market application from which it draws stock-market data.In some embodiments, stock-market complication 5314 can optionally be aselectable affordance, such that detection of a user input at a locationon display 5302 corresponding to stock-market complication 5314 canoptionally cause an associated interface to be displayed, additionalinformation to be displayed, or an associated application (e.g., astock-market application) to be accessed or opened. In some embodiments,stock-market complication 5314 can optionally display information aboutone or more stocks, one or more markets or indexes, one or moreportfolios, or any other relevant or useful stock-market information.

In some embodiments, stock-market complication 5314 can optionallydisplay information corresponding to present information or to pastinformation (e.g., historical information, recorded events, past events,or past predictions/forecasts). In some embodiments, stock-marketcomplication 5314 can optionally be incapable of displaying informationcorresponding to future information, as future stock-market informationmay be un-knowable. In some embodiments, stock-market complication 5314can optionally be configured to display certain future information, suchas scheduled future purchases or sales, scheduled future events (e.g.,markets opening), or projected or predicted future stock marketperformances. In the depicted example, stock-market complication 5314 isdisplaying current stock-market information, indicating that the NASDAQis up 2.45 points on the day.

FIG. 53A further depicts user input 5316 a, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5316 a canoptionally be a single-touch input, a multi-touch input, a single-tapinput, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in display 5302. In the displayed example,input 5316 a is a single-finger, single-tap input detected at a locationon display 5302 corresponding to displayed watch face 5308. Device 5300can optionally be configured, in some embodiments, to, in response todetecting user input 5316 a (or any other suitable predefined userinput, including rotation of a rotatable input mechanism) activate atime-scrubbing mode.

FIG. 53B depicts exemplary user interface 5350, displayed on display5302 of device 5300. Exemplary user interface 5350 shows the manner inwhich, in some embodiments, device 5300 responds to the detection ofinput 5316 a in FIG. 53A. Namely, user interface 5350 shows theactivation, by device 5300, of a time-scrubbing mode and an associatedtime scrubbing interface in accordance with some embodiments.

In the depicted example, interface 5350 retains many of the sameelements and features of interface 5340, including the same prominentwatch face 5308, and the same complications 5312 and 5314. In someembodiments, the visual appearance of one or more of the elements ofinterface 5350 differs from the appearance of a corresponding orassociated element in interface 5340, so as to indicate thattime-scrubbing mode has been activated.

In some embodiments, time-scrubbing mode is a mode of operation of adevice in which a user may indicate, by one or more user inputs, a timeother than a current time. In accordance with the user's indication of apast or future time, a device can optionally display an indication ofthe user's indicated time, and can optionally update one or more userinterface objects in accordance with the user's indicated time. Theupdated user interface objects, such as complications, affordances,icons, or the like, can optionally be updated to show information thatcorresponds to the user's indicated time, which may be called ascrubbing time. Thus, in some embodiments, as a user “scrubs” forward orbackward in time, the scrubbing time is continuously updated, and otherinformation displayed on an interface is correspondingly continuouslyupdated, such that the information displayed on the display continuouslycorresponds to the scrubbing time. In the depicted example of activatingand using a time-scrubbing mode of FIGS. 53A-53C, described in greaterdetail below, a user uses a rotational user input to scrub forward intime from 11:09 (the current time) to 11:34 (a future scrubbing time).In accordance with the forward scrubbing, complications 5312 and 5314are updated to correspond to the future scrubbing time, with weathercomplication 5312 displaying a forecasted air temperature andstock-market complication 5314 ceasing to be displayed (to indicate thatfuture information is unavailable).

In the depicted example, interface 5350 differs from interface 5340 inthat, in the place of clock hands 5310 a and 5310 b, interface 5350includes scrubbing hour hand 5322 a and scrubbing minute hand 5322 b. Insome embodiments, scrubbing hands can optionally be displayed in placeof or in addition to non-scrubbing hands (e.g., hands indicating thecurrent time). In some embodiments, scrubbing hands can optionally havethe same visual appearance as current-time hands, or can optionally havea different appearance from current-time hands. For example, scrubbinghands can optionally be displayed in a different size, shape, color,highlighting, or animation style as current-time hands. In someembodiments, for example, current-time hands (e.g., hands 5310 a and5310 b in FIG. 53A) can optionally be displayed in white, whilescrubbing hands (e.g., hands 5322 a and 5322 b) can optionally bedisplayed in green.

In the depicted example, interface 5350 further differs from interface5340 by including digital clock face 5317, which displays the currenttime (11:09). Interface 5350 further differs from interface 5340 byincluding time difference indicator 5318, which displays an indicationof the difference between the current time and the scrubbing time. Inthe example shown, the scrubbing time is 11:09 and the current time isalso 11:09, as the scrubbing time has not yet been moved away from thecurrent time. Therefore, time difference indicator 5318 indicates thatthere is no difference between the current time and the scrubbing timeby indicating a difference of “+0” minutes.

FIG. 53B further depicts rotational input 5320 a, which is a rotationaluser input detected by rotational input mechanism 5304 of device 5300.Rotational user input 5320 a can optionally include one or morerotations of rotational input mechanism 5304, the one or more rotationseach having one or more speeds, accelerations, directions, durations,and spacings relative to one another. The one or more rotations canoptionally together form a predefined rotation pattern constituting aninput. In the depicted example, rotational input 5320 a is a singlerotation of rotatable input mechanism 5304 in a clockwise direction asdefined if looking at the face of the rotatable input mechanism from inthe plane of the page to the left of the figure. (That is, theillustrated direction of rotation is such that rotatable input mechanism5304 is being rotated into the plane of the page in the z-axis directionat the top of rotatable input mechanism 5304, while it is being rotatedout of the plane of the page in the z-axis direction at the bottom ofrotatable input mechanism 5304.) In some embodiments, rotational input5320 a is an input for scrubbing forward to a future time.

FIG. 53C depicts exemplary user interface 5360 displayed on display 5302of device 5300. Exemplary user interface 5360 shows the manner in which,in some embodiments, device 5300 responds to the detection of input 5320a in FIG. 53B. Namely, user interface 5360 shows time scrubbing to afuture time, by device 5300, and an associated interface in accordancewith some embodiments. Specifically, interface 5360 depicts how watchface 5308 (and hands 5310 a, 5310 b, 5322 a, and 5322 b) andcomplications 5312 and 5314 are updated in accordance with timescrubbing.

First, in the depicted example, in accordance with user input 5320 a,scrubbing hands 5322 a and 5322 b are moved forward to indicate thescrubbing time. In some embodiments, scrubbing hands can optionally bemoved continuously, smoothly, or regularly to match a rotational userinput, such that the further and faster a rotational input rotates, thefurther and faster scrubbing hands can optionally advance. In someembodiments, scrubbing hands can optionally sweep from a previousposition into a current position, simulating the appearance of watchhands sweeping into a new position as the watch is set to a new time byrotating a watch crown. In the depicted example, scrubbing hour hand5322 a and scrubbing minute hand 5322 b have swept from their previousposition in interface 5350 to their new position in interface 5360 (asindicated by the arced arrow showing the movement of scrubbing hour hand5322 b) in accordance with the detection of rotational user input 5320 ain FIG. 53B.

Further, in the depicted example, as scrubbing hands 5322 a and 5322 bsweep forward as the scrubbing time is advanced into the future, hands5310 a and 5310 b, which are current-time hands, are revealed in theirplace. In some embodiments, hands 5310 a and 5310 b are identical inappearance as they were in interface 5340 in FIG. 53A. In someembodiments, hands 5310 a and 5310 b are displayed in a manner tovisually indicate that time-scrubbing mode is active, such as byvisually distinguishing the hands 5310 a and 5310 b from theirappearance when time-scrubbing mode was not active, such as by beingdisplayed in a different size, shape, color, highlighting, or animationstyle. In the depicted embodiment, hands 5310 a and 5310 b are displayedin a white color before the activation of time-scrubbing mode, whilethey are displayed in a gray, partially translucent color intime-scrubbing mode; this gray translucent color is indicated by thehash pattern on hands 5310 a and 5310 b in FIG. 53C. In the depictedexample, hands 5310 a and 5310 b are displayed as being “behind”scrubbing hands 5322 a and 5322 b, as shown by hour scrubbing hand 5322a occluding hour hand 5310 a where the two hands partially overlap; thisarrangement may help emphasize scrubbing hands while in time-scrubbingmode, as the scrubbing hands can optionally be central to thefunctionality of time scrubbing and can optionally correspond to otherinformation displayed on a scrubbing interface.

Further, in the depicted example, digital clock face 5317 and timedifference indicator 5318 have been updated in accordance with thescrubbing time. In the depicted example of interface 5360, digital clockface 5317 has been updated to indicate the new scrubbing time of 11:34,and time difference indicator has been updated to indicate thedifference between the current time (11:09) and the scrubbing time(11:34) of “+25” minutes. In some embodiments, user interface objectssuch as digital clock face 5317 and time difference indicator 5318 canoptionally be continuously or intermittently updated as a user scrubsforward or backward in time. Updates can optionally be displayed foreach changing second, 15 seconds, minute, 5 minutes, hour, or the like.In some embodiments, one or more animations can optionally be used todepict text or numerals changing as the user scrubs forward or backwardin time. In some embodiments, text, numerals, or other characters orelements of a user interface object can optionally be suddenly replacedby a new character as scrubbing is performed, such that the “09” in11:09 would cease to be displayed and be immediately replaced by a “10.”In some embodiments, one or more characters or other elements of a userinterface object can optionally transition by way of an animation; forexample, old elements or characters can optionally fade away by becomingincreasingly translucent, can optionally shrink in size, can optionallytranslate in one or more directions, and/or can optionally be displayedas “flipping” out of view to simulate the appearance of a flap-display,split-flap display, or arrival/departure board; new elements orcharacters can optionally, for example, fade into view by becomingdecreasingly translucent, can optionally grow in size, can optionallytranslate in one or more directions, and/or can optionally be displayedas “flipping” into view to simulate the appearance of a flap-display,split-flap display, or arrival/departure board. In some embodiments, anyof the animations described above or elsewhere in this disclosure canoptionally be reversed, such that an animation can optionally bedisplayed in a first order when a user is scrubbing in a firstdirection, and the animation can optionally be displayed in the oppositeorder (as if rewinding a video) when a user is scrubbing in the oppositedirection.

Further, in the depicted example of FIG. 53C, complications 5312 and5314 have been updated in accordance with the scrubbing to a futuretime, such that the displayed (or newly undisplayed) complicationscorrespond to the displayed scrubbing time by displaying informationrelated to the displayed scrubbing time. Complications can optionally beupdated in time-scrubbing mode such that the information displayed bythe complication corresponds to the currently displayed scrubbing time,rather than the current time. An update to a complication can optionallyinclude, as compared to when the device was not in time-scrubbing modeor was scrubbed to a different scrubbing time, displaying differentinformation, ceasing to display information, or beginning to displayinformation after having ceased to display information.

For example, when a scrubbing time is a future time, displayedcomplications can optionally display future scheduled events such asfuture calendar events, can optionally display forecasted or projectedinformation (such as a weather forecast) or can optionally indicate alack of availability of information corresponding to the future time. Inthe case of a lack of availability of information corresponding to afuture time, a complication can optionally affirmatively indicate thatno information is available via displayed text or symbol, thecomplication can optionally cease to be displayed to indicate that noinformation is available, or the complication can optionally “freeze”and/or be displayed in a manner so as to indicate that the informationdisplayed in the frozen state does not correspond to the future time(e.g., a complication can optionally be grayed out or faded out with thefuture-most available information displayed, if the complication isscrubbed so far into the future that no information for the scrubbingtime is available).

When a scrubbing time is a past time, displayed complications canoptionally display past scheduled events such as a past calendar event,can optionally display previously projected information such as a pastweather forecast (e.g., in the absence of available historical data), orcan optionally indicate a lack of availability of informationcorresponding to the past time. In the case of a lack of availability ofinformation corresponding to a past time, a complication can optionallyaffirmatively indicate that no information is available via displayedtext or symbol, the complication can optionally cease to be displayed toindicate that no information is available, or the complication canoptionally “freeze” and/or be displayed in a manner so as to indicatethat the information displayed in the frozen state does not correspondto the past time (e.g., a complication can optionally be grayed out orfaded out with the oldest available information displayed, if thecomplication is scrubbed so far into the past that no information forthe scrubbing time is available).

In some embodiments, a complication can optionally cease to displayinformation when no information is available for or relevant to acertain period of time. For example, if a complication relates to adaily performance of a stock index, then, as a user scrubs backwardsthrough time, the complication can optionally cease to display anyinformation when the user scrubs to the early morning hours, or to aweekend, when the stock market was not open and no daily performance isconsidered relevant. As a user continues to scrub in the same direction,relevant information can optionally again be displayed as the userscrubs through additional scrubbing times, such as reaching anotherperiod when the stock market was open and beginning to display a dailyperformance for the stock index for that day and time.

In the example depicted in FIG. 53C, a user is scrubbing forward in time(the current time being 11:09, as indicated by hands 5310 a and 5310 b)and has reached 11:34 (as indicated by digital clock face 5317 andscrubbing hands 5322 a and 5322 b) with a time offset of plus 25 minutes(as indicated by time difference indicator 5318). As the user hasscrubbed forward in time by 25 minutes, weather complication 5312 hasbeen updated to reflect a weather forecast for 25 minutes in the future,when it is predicted to be one degree warmer, at 73° rather than thecurrent 72° (as indicated in interface 5350 in FIG. 53B). As the userhas scrubbed forward in time by 25 minutes, stock-market complication5314 has been updated to reflect the fact that information about thefuture performance of the NASDAQ is unavailable; the lack of informationis conveyed by the stock-market complication 5314, as shown in interface5350 in FIG. 53B, ceasing to be displayed in interface 5360 in FIG. 53C.

FIG. 53C further depicts user input 5336 a, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5336 a canoptionally be a single-touch input, a multi-touch input, a single-tapinput, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in display 5302. In the displayed example,input 5336 a is a single-finger, single-tap input detected at a locationon display 5302 corresponding to displayed weather complication. In someembodiments, in response to detecting user input 5336 a, device 5300 canoptionally provide additional information, additional interfaces, oradditional modes corresponding to weather complication 5312. Forexample, device 5300 can optionally launch a weather applicationassociated with weather complication 5312. In some embodiments, device5300 can optionally provide additional information, additionalinterfaces, or additional modes corresponding to a selected complicationand to the scrubbing time. For example, in response to a user tapping aweather complication when the device is scrubbed to a past time, aninterface of a weather application showing historical weather data forthe scrubbed-to past time can optionally be displayed; in response to auser tapping a weather complication when the device is scrubbed to afuture time, an interface of a weather application showing forecastedweather for the scrubbed-to future time can optionally be displayed. Inthe depicted example, in response to detecting user input 5336 a, device5300 can optionally provide current weather information (because thescrubbing time is so close to the present, e.g., below a predefinedthreshold amount of time into the future) in some embodiments, or it canoptionally provide forecasted weather information associated with thescrubbing time of 11:34 in some embodiments.

FIG. 53C further depicts user inputs 5324 a and 5324 b, both of whichare user inputs configured to cause device 5300 to exit time-scrubbingmode and return to a non-time-scrubbing interface. In some embodiments,any suitable user input can optionally be predetermined to cause adevice to exit time-scrubbing mode. In the depicted example, user input5324 a is a touch contact detected on display 5302. In some embodiments,user input 5324 a can optionally be a single-touch input, a multi-touchinput, a single-tap input, and/or a multi-tap input detected by touch-and/or pressure-sensitive elements in display 5302. In some embodiments,user input 5324 a is a single-tap input detected at a locationcorresponding to digital clock face 5317 and/or time differenceindicator 5318. In the depicted example, user input 5324 b is adepression input detected by rotatable and depressible input mechanism5304. In some embodiments, user input 5324 b can optionally be asingle-press input or a multi-press input detected by a rotatable anddepressible input mechanism. In some embodiments, user input 5324 b is asingle-press input detected by depressible and rotatable input mechanism5304.

In response to detecting either user input 5324 a or 5324 b, or anyother suitable predetermined user input, device 5300 can optionallycause time-scrubbing mode to be ceased and can optionally cease todisplay time scrubbing interfaces. In some embodiments, updatedcomplications can optionally return to their original appearance beforetime-scrubbing mode was engaged, or can optionally change to anappearance corresponding to a new current time other than the currenttime that was current when time-scrubbing mode was engaged. In someembodiments, indications that time-scrubbing mode is active, such asdigital clock face 5317, time difference indicator 5318, and scrubbinghands 5322 a and 5322 b can optionally cease to be displayed. In someembodiments, hands corresponding to a current time, such as hands 5310 aand 5310 b, can optionally return to their original visual appearanceand style from before time-scrubbing mode was engaged. Any of thesechanges can optionally be made by way of any of the animations describedabove, including a reversed and/or accelerated version of any suchanimation. In the depicted example, in response to detecting user input5324 a or 5324 b, device 5300 ceases to display user interface 5360 anddisplays user interface 5340 again; user interface 5340 indicates thatthe current time is still 11:09 and that the information correspondingto both weather complication 5312 (72°) and stock-market complication5314 (NASDAQ +2.45) has not changed since time-scrubbing mode wasactivated.

Attention is now specifically directed to interfaces for time scrubbinga digital clock face. In the depicted example of activating and using atime-scrubbing mode of FIGS. 53D-53F, described in greater detail below,a user uses a rotational user input to scrub forward in time from 11:09(the current time) to 11:34 (a future scrubbing time). In accordancewith the forward scrubbing, complications 5312 and 5314 are updated tocorrespond to the future scrubbing time, with weather complication 5312displaying a forecasted air temperature and stock-market complication5314 ceasing to be displayed (to indicate that future information isunavailable).

FIG. 53D depicts exemplary user interface 5370, displayed on display5302 of device 5300. In some embodiments, user interface 5370 is a watchface interface screen, such as a home interface of a wearablesmart-watch portable electronic device. In some embodiments, interface5370 can optionally be displayed by device 5300 in response to a user(such as a user of a device displaying interface 5340 as described inFIG. 53A) selecting a different “face” for device 5300, for examplecausing interface 5340 to cease to be displayed and interface 5370 tobegin to be displayed. Interface 5370 can optionally share some commonelements with interface 5340, namely weather complication 5312 andstock-market complication 5314. In some embodiments, complications 5312and 5314 in interface 5370 can optionally have some or all of theattributes as described above with reference to interface 5340 in FIG.53A.

Interface 5370 includes digital watch face 5328, which is indicatingthat the current time is 11:09. Interface 5370 also includes day/dateobject 5326, which is indicating that the current day of the week isTuesday and that the current date is July 10. In some embodiments,day/date object 5326 can optionally be considered a complication, andcan optionally be referred to as a day/date complication.

FIG. 53D further depicts user input 5316 b, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5316 b canoptionally be a single-touch input, a multi-touch input, a single-tapinput, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in display 5302. In the displayed example,input 5316 b is a single-finger, single-tap input detected at a locationon display 5302 corresponding to digital clock face 5328. Device 5300can optionally be configured, in some embodiments, to, in response todetecting user input 5316 b (or any other suitable predefined userinput, including rotation of a rotatable input mechanism), activate atime-scrubbing mode.

FIG. 53E depicts exemplary user interface 5380, displayed on display5302 of device 5300. Exemplary user interface 5380 shows the manner inwhich, in some embodiments, device 5300 responds to the detection ofinput 5316 b in FIG. 53D. Namely, user interface 5380 shows theactivation, by device 5300, of a time-scrubbing mode and an associatedtime scrubbing interface in accordance with some embodiments.

In the depicted example, interface 5380 includes object 5326 andcomplications 5312 and 5314 in the same manner as described above withreference to interface 5370 in FIG. 53D. In some embodiments, object5326 and complications 5312 and 5314 can optionally be visuallydistinguished in one or more ways from their respective appearances ininterface 5370 in FIG. 53D to indicate that time-scrubbing mode isactive.

In the depicted example, interface 5380 differs from interface 5370 inseveral ways that indicate that time-scrubbing mode has been activated.In the depicted example, interface 5380 differs from interface 5370 inthat digital clock face 5328 has translated to the top right corner ofdisplay 5302 (as indicated by the diagonal arrow) and has decreased insize. In some embodiments, this transition can optionally include ananimation of the translation and the resizing. In some embodiments, whendigital clock face 5328 is moved from its position in interface 5370 toits position in interface 5380, it can optionally be displayed in adifferent size, shape, color, highlighting, or animation style. In someembodiments, the shape, color, highlighting, and/or animation style ofdigital clock face 5328 can optionally remain unchanged as digital clockface translates and is resized between interface 5370 in FIG. 53D andinterface 5380 in FIG. 53E. In some embodiments, digital clock face 5328can optionally appear in a white color in both interfaces 5370 andinterface 5380.

In some embodiments, when digital clock face 5328 transitions to the topcorner of display 5302 as time-scrubbing mode is activated, a visualindicator indicating that digital clock face 5328 indicates a currenttime can optionally be displayed. In the depicted example, the word“NOW” is displayed on display 5302 near the top left corner of display5302. In some embodiments, the visual indicator, such as the word “NOW,”can optionally be displayed in a similar or identical visual style asdigital clock face 5328 following its transition into its position ininterface 5380. For example, the word “NOW” can optionally be displayedin a similar size, font, color, highlighting, and/or animation style asdigital clock face 5328 in interface 5380. In the depicted example, theword “NOW” or another indicator can optionally appear in a white colorwhen digital clock face 5328 appears in a white color.

In the depicted example, interface 5380 further differs from interface5370 by including digital clock face 5332, which is a second digitalclock face that has appeared in the position on display 5302 that waspreviously occupied by digital clock face 5328 (before its transitionand resizing) in interface 5370 in FIG. 53D. In some embodiments,digital clock face 5332 displays the scrubbing time of time-scrubbingmode, which currently is 11:09, the same as the current time, as theuser has not entered any input causing the scrubbing time to advanceinto the future or rewind into the past. In some embodiments, digitalclock face 5332 can optionally be displayed in the same or similarvisual style as digital clock face 5328, including by being displayed inthe same size, font, color, highlighting, and/or animation style. Insome embodiments, digital clock face 5332 can optionally be displayed ina different visual style than digital clock face 5328 in interface 5370,to indicate to the user that digital clock face 5332 indicates ascrubbing time rather than a current time, such as by being displayed ina green color rather than a white color. In some embodiments, digitalclock face 5332 can optionally appear on interface 5380 in response tothe activation of time-scrubbing mode in accordance with any of theanimations discussed above with reference to complications being updatedduring scrubbing. In some embodiments, the animation of digital clockface 5332 appearing in interface 5380 can optionally include digitalclock face 5380 increasing in size and/or gradually becoming lesstranslucent (e.g., fading in).

FIG. 53E further depicts rotational input 5320 b, which is a rotationaluser input detected by rotational input mechanism 5304 of device 5300.In some embodiments, rotational user input 5320 b can optionally haveone or more characteristics in common with rotational input 5320 adescribed above with reference to FIG. 53B. In some embodiments,rotational input 5320 b is an input for scrubbing forward to a futuretime.

FIG. 53F depicts exemplary user interface 5390 displayed on display 5302of device 5300. Exemplary user interface 5390 shows the manner in which,in some embodiments, device 5300 responds to the detection of input 5320b in FIG. 53E. Namely, user interface 5390 shows time scrubbing to afuture time by device 5300 and an associated interface in accordancewith some embodiments. Specifically, interface 5390 depicts how digitalclock face 5332 and complications 5312 and 5314 are updated inaccordance with time scrubbing.

First, in the depicted example, in accordance with user input 5320 b,digital clock face 5332 has changed from displaying “11:09” to insteaddisplaying “11:24,” thereby indicating the scrubbing time. In someembodiments, a digital clock face can optionally be stepped forward inaccordance with a rotational user input, such that the further andfaster a rotational input rotates, the further and faster a digitalclock face indicating a scrubbing time can optionally advance. In someembodiments, displayed numerals on a digital clock face can optionallychange iteratively, such as once for every minute scrubbed, once forevery five minutes scrubbed, or the like. Updates can optionally bedisplayed for each changing second, 15 seconds, minute, 5 minutes, hour,or the like. In some embodiments, displayed numerals on a digital clockface can optionally change gradually or smoothly, such as by fading intoand out of view or translating into or out of view. In some embodiments,displayed numerals on a digital clock face can optionally be animated aschanging individually (e.g., number by number), and in some embodimentsdisplayed numerals on a digital clock face can optionally be animated aschanging as a group (e.g., part of, or the entire, digital clock facechanges together). In some embodiments, one or more of the numerals orother elements displayed as part of a digital clock face, includingdigital clock face 5332, can optionally change in any of the mannersdescribed above with reference to digital clock face 5317 and FIG. 53C,including by way of an animation simulating the appearance of aflap-display, split-flap display, or arrival/departure board.

Further, in the depicted example, as digital clock face 5332 advancesfurther as the scrubbing time is advanced into the future, digital clockface 5328 can optionally remain fixed and continue to display thecurrent time. (If the current time advances with the passage of time,digital clock face 5328 can optionally accordingly advance, and ascrubbing clock face such as digital clock face 5332 can optionally alsoaccordingly advance to maintain the same offset between the current timeand the scrubbing time.) In some embodiments, a time differenceindicator can optionally be displayed as part of user interface 5390(and/or 5380 in FIG. 53E), and the time difference indicator canoptionally be updated (in accordance, in some embodiments, with any ofthe animations or display styles discussed above, including thosediscussed with reference to digital clock face 5332 and/or thosediscussed with reference to digital clock face 5317 and FIG. 53C) todisplay an updated time difference in accordance with the scrubbing timeadvancing further into the future. If user interface 5390 included atime difference indicator, for example, it would be updated inaccordance with the time being scrubbed forward to indicate a positive25 minute difference between the scrubbing time of 11:34 and the currenttime of 11:09.

Further, in the depicted example of FIG. 53F, complications 5312 and5314 have been updated in the same manner as described above withreference to interface 5360 in FIG. 53C, so as to correspond to thescrubbing time of 11:34 rather than the current time of 11:09. In someembodiments, day/date object 5326 can optionally also be updated inaccordance with a scrubbing time in time-scrubbing mode; for example, ifa user scrubs far enough into the future or the past to reach adifferent day, then day/date object 5326 can optionally be updated in asame or similar manner as a complication can optionally be updated toreflect the change to the day and date.

FIG. 53F further depicts user input 5336 b, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5336 b canoptionally be a single-touch input, a multi-touch input, a single-tapinput, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in display 5302. In the displayed example,input 5336 b is a single-finger, single-tap input detected at a locationon display 5302 corresponding to displayed weather complication. In someembodiments, in response to detecting user input 5336 a, device 5300 canoptionally provide additional information, additional interfaces, oradditional modes corresponding to weather complication 5312, includingin any of the manners described above with respect to input 5336 a andFIG. 53C.

FIG. 53F further depicts user inputs 5334 a and 5334 b, both of whichare user inputs configured to cause device 5300 to exit time-scrubbingmode and return to a non-time-scrubbing interface. In some embodiments,any suitable user input can optionally be predetermined to cause adevice to exit time-scrubbing mode. In some embodiments, user inputs5334 a and 5334 b can optionally share some or all characteristics withuser inputs 5324 a and 5324 b described above, respectively.

In response to detecting either user input 5334 a or 5334 b, or anyother suitable predetermined user input, device 5300 can optionallycause time-scrubbing mode to be ceased and can optionally cease todisplay time scrubbing interfaces. In some embodiments, updatedcomplications can optionally return to their original appearance beforetime-scrubbing mode was engaged, or can optionally change to anappearance corresponding to a new current time other than the currenttime that was current when time-scrubbing mode was engaged. In someembodiments, indications that time-scrubbing mode is active, such asdigital clock face 5332, can optionally cease to be displayed, and userinterface objects that moved position and/or changed appearance, such asdigital clock face 5328, can optionally return to their original visualappearance and style from before time-scrubbing mode was activated. Anyof these changes can optionally be made by way of any of the animationsdescribed above, including a reversed and/or accelerated version of anysuch animation. In the depicted example, in response to detecting userinput 5334 a or 5334 b, device 5300 ceases to display user interface5390 and displays user interface 5370 again; user interface 5370indicates that the current time is still 11:09 and that the informationcorresponding to both weather complication 5312 (72°) and stock-marketcomplication 5314 (NASDAQ +2.45) has not changed since time-scrubbingmode was activated.

FIGS. 54A-54E are flow diagrams illustrating a method for accessing andpresenting information corresponding to past times and future times.Method 700 is performed at a device (e.g., 100, 300, 500, 5300) with adisplay and a rotatable input mechanism. Some operations in method 700can optionally be combined, the order of some operations can optionallybe changed, and some operations can optionally be omitted.

As described below, method 700 provides an intuitive way to access andpresent information corresponding to past times and future times. Themethod reduces the cognitive burden on a user for accessing andpresenting information corresponding to past times and future times,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to access andpresent information corresponding to past times and future times, suchas in a time-scrubbing mode in which displayed complications canoptionally be scrubbed forward and/or backward in time, conserves powerand increases the time between battery charges, by reducing the numberof inputs required, reducing processing power used, and/or reducing thetime of usage of the device.

In some embodiments, a device can optionally display a current-timeindicator displaying a current time. In response to a user input (suchas a tap on a touch-sensitive display on the current-time indicator),the device can optionally display, in addition to the current-timeindicator, a non-current-time indicator. In response to and inaccordance with a user input (such as a rotation of a rotatable inputmechanism such as a crown of a smart watch), the time displayed by thenon-current-time indicator can optionally be scrubbed forward orbackward. In accordance with the scrubbing of the non-current time to afuture or past time, one or more complications or other user interfaceobjects can optionally be updated to correspond to the non-current time,by displaying information relating to the complication and correlatingto the non-current time rather than the current time.

In FIG. 54A, at block 5402, method 700 is performed at an electronicdevice having a display and a rotatable input mechanism. An exemplarydevice is device 5300 of FIGS. 53A-53F, which has display 5302 and has arotatable input mechanism 5304.

A block 5404, the device displays a first current-time indicatorindicating a current time. In some embodiments, a current-time indicatoris any watch face, clock face, or other indication of a time that isconfigured, designed, or understood to display a current time, such asthe current time of day in the timezone in which a user is currentlylocated. In some situations, a current-time indicator can optionally bedisplaying a non-current time, such as when the watch is not set for thecorrect time; however, in most situations, a current-time indicator willdisplay the correct current time. In the example of interface 5340 inFIG. 53A, watch face 5308 and clock hands 5310 a and 5310 b togetherform a current-time indicator, indicating that the current time is11:09. In the example of interface 5370 in FIG. 53D, digital clock face5328 is a current-time indicator, indicating that the current time is11:09.

At block 5406, the device displays a first user interface objectconfigured to display information corresponding to the current time,wherein the information corresponding to the current time pertains to afirst information source and is information other than a day, time, ordate of the current time. In some embodiments, the first user interfaceobject can optionally be a complication, as described above, and canoptionally be configured to display information corresponding to acertain subject matter or a certain information source. In someembodiments, complications can optionally correspond to weatherinformation, to stock market information, to calendar information, today/date information, to time information, to world clock information,to social media information, to message information, to emailinformation, to pedometer information, to health/fitness information, toexercise information, to alarm information, to stopwatch information, toinformation associated with third-party applications, or to any othersuitable information that can optionally be visually presented as partof a complication or other user interface object. In the examples ofinterfaces 5340 and 5370 in FIGS. 53A and 53D, weather complication 5312is a user interface object configured to display informationcorresponding to the current time (e.g., current information), theinformation pertaining to a weather application and/or a source ofweather data in some embodiments. In some embodiments, weathercomplication 5312 can optionally be configured to display currentweather information for the current time, such as a current airtemperature (e.g., 72°). In the examples of interfaces 5340 and 5370 inFIGS. 53A and 53D, stock-market complication 5314 is a user interfaceobject configured to display information corresponding to the currenttime (e.g., current information), the information pertaining to astock-market application and/or a source of stock-market data, in someembodiments. In some embodiments, stock-market complication 5314 canoptionally be configured to display a current performance of the NASDAQ,such as points gained or lost on the current day of trading (e.g., plus2.45 points).

In some embodiments, user interface objects or complications canoptionally be configured to display information that is the most currentinformation available, such as a most recent temperature reading or amost recent stock score. In some embodiments, user interface objects orcomplications can optionally be configured to display information thatexplicitly relates to the current time, such as a calendar event that isoccurring at the current time, or a proximate calendar event that isoccurring at a time in the near future or a time in the near past withreference to the current time.

At block 5408, optionally, the device detects a first touch contact at alocation corresponding to the first current-time indicator. In someembodiments, the input can optionally be one or more touch contactsdetected by a touch-sensitive and/or pressure-sensitive surface, such asa touch-screen. In some embodiments, the first touch contact canoptionally be detected at a location on a touch-screen at which thefirst current-time indicator is currently displayed. In someembodiments, a user can optionally tap a current-time indicator such asa displayed watch face or a digital clock face, and a device canoptionally responsively activate a time-scrubbing mode and displayassociated time-scrubbing interfaces. In the example of interface 5340in FIG. 53A, device 5300 detects user input 5316 a, which is a touchcontact detected by touch-sensitive display 5302. In some embodiments,user input 5316 a is a single-finger single-tap gesture detected at alocation of display 5302 at which watch face 5308 is currentlydisplayed. In the example of interface 5370 in FIG. 53D, device 5300detects user input 5316 b, which is a touch contact detected bytouch-sensitive display 5302. In some embodiments, user input 5316 b isa single-finger single-tap gesture detected at a location of display5302 at which digital clock face 5328 is currently displayed.

At block 5410, optionally, in response to detecting the first touchcontact, the device displays a non-current-time indicator indicating thecurrent time. In some embodiments, when time-scrubbing mode isactivated, a non-current-time indicator is displayed. A non-current-timeindicator can optionally be any watch face, clock face, or otherindication of a time that is configured, designed, or understood todisplay a non-current time. In some embodiments, a non-current-timeindicator can optionally indicate a “scrubbing time” that is displayedwhen time-scrubbing mode is activated; the scrubbing time can optionallybe a time that is set in accordance with user inputs and is used tochange what information is displayed by complications or other userinterface objects during time-scrubbing mode. In some embodiments, thenon-current-time indicator can optionally suddenly appear upon theactivation of time-scrubbing mode, while in some embodiments thenon-current-time indicator can optionally appear by way of animationsuch as translating into position or gradually becoming less transparent(e.g., fading in).

In some embodiments, a scrubbing time, such as one displayed on ascrubbing watch face or a scrubbing clock face, can optionally be set inaccordance with user inputs, and can optionally also be set to thecurrent time (such that the scrubbing time and the current time canoptionally be the same time). In some embodiments, when a time-scrubbingmode is initially activated and a user input or instruction has not yetbeen received to set a scrubbing time, the scrubbing time isautomatically set to the current time as a starting point. In this way,in some embodiments, a non-current-time indicator such as a scrubbingwatch face or a scrubbing clock face can optionally sometimes displaythe current time. In such instances, despite the non-current-timeindicator displaying a time that is the same as the current time, a usermay understand that the non-current-time indicator is not an indicationof the current time per se, but rather an indication that a scrubbingtime is set to a time that is the same as the current time.

In the depicted example of interface 5350 of FIG. 53B, time-scrubbingmode has been activated and, accordingly, scrubbing hands 5322 a and5322 b have been displayed in the same position that hands 5310 a and5310 b were displayed prior to the activation of time-scrubbing mode. Insome embodiments, scrubbing hands 5322 a and 5322 b are non-current-timeindicators configured to indicate a scrubbing time, although in theexample of interface 5350 of FIG. 53B, they are presently indicating ascrubbing time that is the same as the current time of 11:09.

In the depicted example of interface 5380 in FIG. 53E, time-scrubbingmode has been activated and, accordingly, digital clock face 5332 hasbeen displayed in the same position that digital clock face 5328 wasdisplayed prior to the activation of time-scrubbing mode. In someembodiments, digital clock face 5332 is a non-current-time indicatorconfigured to indicate a scrubbing time, although in the example ofinterface 5380 in FIG. 53E, it is presently indicating a scrubbing timethat is the same as the current time of 11:09.

In some embodiments, such as when a user executes multiple user inputsto scrub a scrubbing time forward and then backward, or backward andthen forward, to return the scrubbing time to zero, a non-current-timeindicator indicating the current time can optionally also beresponsively displayed.

At block 5412, the device detects a first rotation of the rotatableinput mechanism. In some embodiments, a first rotation of the rotatableinput mechanism can optionally comprise one or more rotations in one ormore directions, having one or more speeds, having one or moredurations, and having one or more spacings relative to one another. Insome embodiments, a first rotation of the rotatable input mechanism canoptionally comprise a single rotation of a rotatable input mechanism ina predefined rotational direction. In some embodiments, a user canoptionally rotate a rotatable input mechanism in a first direction, anda device can optionally responsively scrub a scrubbing time forward intothe future (or, in some embodiments, backward into the past). In someembodiments, the first rotation of a rotatable input mechanism canoptionally begin to be detected when a time-scrubbing mode is inactive,while in some embodiments it can optionally begin to be detected while atime-scrubbing mode is already activated. In the depicted examples ofFIGS. 53B and 53E, rotational inputs 5320 a and 5320 b are detected bydevice 5300 when a user rotates rotatable input mechanism 5304 in afirst direction.

In FIG. 54B, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism. In FIG. 54B, block 5414 follows from block5412.

At block 5414, blocks 5416 to 5442 (some of which are optional), shownin FIGS. 54B and 54C, are performed in response to detecting the firstrotation of the rotatable input mechanism. In discussing blocks 5416 to5442 below, the phrase “in response to detecting the first rotation ofthe rotatable input mechanism” may or may not be repeated for clarity.In some embodiments, method steps are performed in response to detectingrotation of a rotatable input mechanism, which can optionally be theprimary input mechanism for driving functionality in a time-scrubbingmode. That is, in some embodiments, rotation of a rotatable inputmechanism can optionally be the core manner in which a user scrubs timeforward or scrubs time backward, and various elements of the userinterface objects can optionally react accordingly to the user'srotational input commands.

At block 5416, in response to detecting the first rotation of therotatable input mechanism, the device displays a non-current-timeindicator indicating a first non-current time determined in accordancewith the first rotation. In some embodiments, the first non-current-timeindicator can optionally be any of the non-current-time indicatorsdescribed above with reference to block 5410, or can optionally sharesome or all of the characteristics of the non-current-time indicatorsdescribed above. In some embodiments, in contrast to thenon-current-time indicator in block 5410, the non-current-time indicatordisplayed in block 5414 (which can optionally be a differentnon-current-time indicator or the same non-current-time indicator)indicates a non-current time that is determined in accordance with thefirst rotation. In some embodiments, the indicated non-current time is ascrubbing time, and the scrubbing time is determined in accordance witha user's rotational scrubbing input.

In some embodiments, when the rotational input is detected before theactivation of time-scrubbing mode, a non-current-time indicator, such asa scrubbing-time digital clock face or scrubbing hands on an analogclock face, can optionally begin to be displayed and display auser-selected scrubbing time. In some embodiments, when the rotationalinput is detected once a time-scrubbing mode has already been activated,then a previously displayed non-current-time indicator can optionally bemodified to display a newly selected scrubbing time.

In some embodiments, a scrubbing time for a time-scrubbing mode canoptionally be selected in accordance with a characteristic of therotational input, and the selected scrubbing time can optionally bedisplayed by the non-current-time indicator. In some embodiments, thenon-current-time indicator can optionally display an animation of theindicator changing to the newly selected scrubbing time, including anyof the animation styles discussed above with reference to digital clockface 5317 and FIG. 53C. In some embodiments, an animation can optionallyinclude displaying clock hands (e.g., a minute hand and an hour hand)sweeping into new positions.

In some embodiments, a rotation of a rotational input mechanism in onedirection can optionally cause scrubbing forward, while a rotation ofthe rotational input mechanism in a direction substantially opposite tothe one direction can optionally cause scrubbing backward. In someembodiments, the rate of scrubbing (forward or backward) can optionallybe proportionally related to the rate of rotation; in some embodiments,the amount of time scrubbed can optionally be proportionally related tothe distance (e.g., angular rotation) of rotation. In some embodiments,the scrubbing rate and amount of time scrubbed can optionally simulatethe effect of a watch crown, where clock hands are physically connectedto the crown by a series of gears, and accordingly the movement of thehands follows a user's twisting of the crown, reflecting a rotation ofthe crown by way of a predefined gear ratio. (In some embodiments, therate and distance of scrubbing of a digital clock face can optionally bethe same as the rate and distance of scrubbing of a displayed likenessof an analog clock face.)

In some embodiments, a device can optionally provide different“gearings” for different available faces. That is, a user can optionallyselect between more than one watch or clock interface, and, depending onthe interface selected, the speed and distance of scrubbing in responseto a given rotational input can optionally vary. For example, in someembodiments, an interface displaying (as a time indicator) a likeness ofthe globe can optionally display one rotation of the globe(approximately 24 hours) in response to a first rotation of therotational input. Meanwhile, in some embodiments, an interfacedisplaying (as a time indicator) a likeness of the solar system canoptionally display one revolution of the Earth (approximately 365 days)in response to the same first rotation of the rotational input.Differences in the amount of time scrubbed in response to a givenrotational input can optionally similarly be provided between otherwatch faces, such as an analog face like the one shown in interface 5340in FIG. 53A, or a digital face such as the one shown in interface 5370in FIG. 53D.

In some embodiments, the rate of time scrubbing and/or the amount oftime scrubbed in response to a rotational input can optionally not havea fixed relationship to the angular magnitude of the rotational input.That is, in some embodiments, a rotational input of a given angularmagnitude can optionally result in different amounts of time scrubbed,depending on various other factors. As discussed above, in someembodiments, different interfaces can optionally be associated withdifferent default gearings. In some embodiments, a user can optionallymanually select different gearings, for example by executing an input ona displayed user interface object or by executing an input by actuatinga hardware button (e.g., executing one or more presses of a rotatableand depressible input mechanism).

In some embodiments, a gearing can optionally not be fixed, such that,during the course of an ongoing rotational input, the relative rate(e.g., instantaneous rate) of time scrubbing as compared to the rate(e.g., instantaneous rate) of rotation of the rotatable input mechanismcan optionally be increased and/or decreased. For example, a variablegearing can optionally be configured such that rotation below athreshold speed (e.g., angular rotation per second) causes timescrubbing at a first rate or a first gearing, while rotation above thethreshold speed causes time scrubbing at an accelerated rate or anaccelerated fearing. In this way, when a user wishes to scrub by a largeamount of time, the device can optionally recognize their rapid rotationof the rotational input mechanism and accordingly accelerate the timescrubbing rate, helping the user to more easily scrub by a largedistance. In some embodiments, during an ongoing rotational input, ifthe speed of a rotational input drops below a predefined speed thresholdafter the time scrubbing rate has been accelerated, then the timescrubbing rate can optionally be decelerated and/or returned to itsoriginal rate; this deceleration may aid a user who has used acceleratedscrubbing to move the scrubbing time by a large amount, enabling theuser to more precisely set the final desired scrubbing time as the userbegins to slow his rotational input. In some embodiments, gearing canoptionally be dynamically varied in accordance with any characteristicof a user input, such as a speed, a direction, a distance (e.g., angulardistance), and/or a pressure.

In some embodiments in which a time scrubbing speed is accelerated, itshould be noted that an animation of time scrubbing can optionally bedifferent for accelerated scrubbing than for non-accelerated scrubbing.For example, in some embodiments, for non-accelerated scrubbing, adevice can optionally provide a first animation of numbers on a digitalclock face changing (with or without an accompanying animation such as atranslation or a flipping effect) or a first animation of a minute handand an hour hand sweeping around a clock face. Meanwhile, in someembodiments, for accelerated scrubbing, a device can optionally provideone or more different animations, such as blurring numbers on a digitalclock face to signify that they are being changed rapidly, or byproviding an animation of a blurred minute hand (or hiding a minute handaltogether) in order to avoid the minute hand appearing to “jump” fromone position to another on a display without sweeping throughintermediate positions. In some embodiments, such alternate animationsfor accelerated scrubbing can optionally be provided as part of anaccelerated scrubbing mode, sometimes called a “turbo mode.”

In some embodiments, a scrubbing time can optionally be set partially inaccordance with a user's input and partially in accordance withpredefined scrubbing times. For example, in some embodiments, predefinedscrubbing times can optionally be configured such that, when a userexecutes an input that would set a scrubbing time to a predefined rangeof times, the actual scrubbing time is set to a predefined time. Forexample, if a predefined scrubbing time is 12:00 noon, and the userrotates a rotational input mechanism an appropriate distance and speedto set the scrubbing time to 11:58, then the scrubbing time canoptionally be rounded to 12:00 noon and set to 12:00 noon. The range ofscrubbing times that will “snap” to a predefined scrubbing time canoptionally be set to any suitable length of time, such as one minute,five minutes, 15 minutes, 30 minutes, one hour, six hours, 12 hours, 24hours, 2 days, one week, one month, one year, etc. In some embodiments,a device can optionally snap to different predefined scrubbing timesdepending on what interface a user is using; for example, in aninterface featuring a likeness of the Earth or a representation of thesun, the device can optionally be configured to “snap” to scrubbingtimes to times corresponding to sunset, sunrise, or high noon. Asanother example, in interfaces featuring a likeness of the solar system,the device can optionally be configured to “snap” to scrubbing timescorresponding to astronomical events such as planet alignments oreclipses.

In some embodiments, predefined scrubbing times can optionally bedetermined in accordance with user input. In some embodiments, a usercan optionally manually set predefined scrubbing times, such as bysetting “snap” times or selecting a “snap” interval. In someembodiments, predefined scrubbing times can optionally be set inaccordance with data or information relating to one or more userinterface objects or complications. For example, a device can optionallybe configured to round a scrubbing time to the time at which a calendarevent begins or ends. In some embodiments, a device can optionally beconfigured to round a scrubbing time to times at which data for acomplication changes, becomes available, or ceases to be available. Insome embodiments, a device can optionally be configured to slow or stopa scrubbing rate in accordance with a calendar event or other scheduledevent being reached while scrubbing forward or backward, and a devicecan optionally be configured to snap or round a scrubbing time to a timecorresponding to the calendar event or scheduled event.

In the depicted example of interface 5360 in FIG. 53C, scrubbing hands5322 a and 5322 b have swept smoothly forward from their previousposition in interface 5350 in FIG. 53B, moving forward in time inaccordance with the speed and magnitude of user input 5320 a in FIG.53B, to indicate in user interface 5360 that the scrubbing time has beenset to the non-current time of 11:34, which is 25 minutes ahead of thecurrent time of 11:09. In the depicted example of interface 5390 in FIG.53F, the numerals in digital clock face 5332 have changed in accordancewith the speed and magnitude of user input 5320 b in FIG. 53C toindicate in user interface 5390 that the scrubbing time has been set tothe non-current time of 11:34, which is 25 minutes ahead of the currenttime of 11:09.

At block 5418, optionally, the first non-current time is a future time.In some embodiments, a non-current scrubbing time can optionally be atime that is in the future as compared to the current time. In someembodiments, a user can optionally scrub to a future time in atime-scrubbing mode by executing a rotation of a rotatable inputmechanism in a predefined direction. A predefined direction of rotationfor scrubbing into the future can optionally be substantially oppositeto a predefined direction of rotation for scrubbing into the past. Inthe examples of interfaces 5360 and 5390 in FIGS. 53C and 53F,respectively, the scrubbing time is a future time of 11:34, which is 25minutes ahead of the current time of 11:09.

At block 5420, optionally, the first non-current time is a past time. Insome embodiments, a non-current scrubbing time can optionally be a timethat is in the past as compared to the current time. In someembodiments, a user can optionally scrub to a past time in atime-scrubbing mode by executing a rotation of a rotatable inputmechanism in a predefined direction. A predefined direction of rotationfor scrubbing into the past can optionally be substantially opposite toa predefined direction of rotation for scrubbing into the future.

At block 5421, the non-current-time indicator is displayed at a locationat which the first current-time indicator was displayed before thedetection of the first rotation of the rotatable input mechanism. Insome embodiments, a non-current-time indicator, such as one that isnewly displayed upon the activation of time-scrubbing mode, canoptionally be displayed at a location at which a current-time indicatorwas previously displayed before the activation of time-scrubbing mode.In some embodiments, the non-current-time indicator can optionallyappear in its displayed position by way of any of the animationsdiscussed above with reference to digital clock face 5317 and FIG. 53C.In some embodiments, a current-time indicator such as a digital clockface can optionally be animated as translating out of the way, and anon-current-time indicator, such as a different digital clock face withnumerals displayed in a different color, can optionally be animated asincreasing in size as if appearing from the distant z-axis and movingtoward the viewer. In some embodiments, a scrubbing time indicator canoptionally replace the current-time indicator on the display. In theexample depicted in interfaces 5380 and 5390 of FIGS. 53E and 53F,digital clock face 5332 is displayed at the same location on display5302 that digital clock face 5323 (which is reduced in size andtranslated to the upper corner upon the activation of time-scrubbingmode) was displayed in interface 5370 in FIG. 53D before the activationof time-scrubbing mode. In the example of interface 5350 in FIG. 53B,scrubbing hands 5322 a and 5322 b are displayed in the same position andsame orientation as hands 5310 a and 5310 b were previously displayed,though scrubbing hands 5322 a and 5322 b can optionally be displayed inthe depicted position in response to a touch contact activatingtime-scrubbing mode; after a rotational input while in time-scrubbingmode, scrubbing hands 5322 a and 5322 b can optionally be displayed at adifferent orientation (e.g., indicating a different time) though in thesame general position (e.g., with the same center/anchor point) as hands5310 a and 5310 b were previously displayed, as depicted in interface5360 of FIG. 53C.

At block 5422, in response to detecting the first rotation of therotatable input mechanism, the device updates the first user interfaceobject to display information corresponding to the first non-currenttime, wherein the information corresponding to the first non-currenttime pertains to the first information source and is information otherthan a day, time, or date of the first non-current time. In someembodiments, when a user executes a rotational input as a command toscrub time forward or backward, one or more user interface objectsdisplayed on a user interface, such as one or more complications, canoptionally be updated in accordance with the newly selected scrubbingtime. In some embodiments, a user interface object or a complication canoptionally be predetermined to correspond to a first information source,subject matter, and/or a first application, and scrubbing time forwardor backward will not change the information source, subject matter, orapplication to which a complication or user interface object pertains.For example, in some embodiments, when a complication is configured todisplay information pertaining to the weather obtained from a weatherapplication, scrubbing the time forward or backward can optionally notchange that the complication displays weather information obtained froma weather application—rather, the change can optionally be with respectto the time (rather than subject matter or information source) to whichthe displayed information pertains. That is, if the weather complicationis configured to display current weather information (e.g., the mostup-to-date temperature reading available) when a device is not intime-scrubbing mode, then scrubbing the time forward can optionallycause the weather complication to instead display forecasted orprojected weather information, while scrubbing the time backward canoptionally cause the device to display historical weather information(or past projected weather information) in some embodiments.

In some embodiments, information can optionally be considered tocorrespond to a time when the information is stored, linked, tagged, orassociated with metadata indicating that the information corresponds tothat time. For example, a piece of information (such as a weatherforecast) can optionally be stored locally or remotely from the device,and can optionally be associated with a metadata or other tag thatindicates a future time to which the weather forecast data corresponds(e.g., the time for the weather forecast). In some embodiments, as auser scrubs forward or backward through time, the device can optionallydetermine when to display the weather forecast data by comparing thedisplayed scrubbing time to the time associated with the tag or metadataof the stored weather forecast (or other stored data entry).

In some embodiments, a user interface object such as a complication canoptionally be updated dynamically as a user scrubs time forward and/orscrubs time backward. In some embodiments, information displayed by acomplication can optionally be updated with each displayed change to thenon-current-time indicator, or it can optionally be updated inaccordance with predefined periods of scrubbing time (e.g., 5 minutes,15 minutes, 1 hour, 1 day, etc.). In some embodiments, informationdisplayed by a complication can optionally be updated as frequently asnew or different information from the currently displayed information isavailable; for example, if a weather forecast predicts a steadytemperature for the next hour, and then an increase by one degree, thena complication displaying a weather temperature can optionally notdisplay any change as the user scrubs through the first hour, then canoptionally display the increased temperature when the scrubbing timereaches the time at which the forecasted temperature changes.

In some embodiments, a user interface object such as a complication canoptionally be updated by way of an animation, including any of theanimations described above with reference to digital clock face 5317 andFIG. 53C. In some embodiments, when a numeral displayed by an animationis changed, a sudden cut or a hard cut transition can optionally beused. In some embodiments, when a change other than a single numeralbeing changed is made to a complication, a transition animation canoptionally be displayed in which a previous portion of (or all of) thecomplication is displayed as translating upwards (e.g., as if beingflipped and rotated upward about a point of connection at the top of thecomplication, in the manner in which a page can optionally be flippedupward on a notepad), shrinking in size, and/or fading away (e.g.,becoming increasingly transparent in time); while a new portion of (orall of) the complication can optionally be displayed as increasing insize (as if translating in from the distant z-axis and moving toward theviewer) and/or fading into view (e.g., becoming decreasingly transparentin time).

In the example of interfaces 5360 and 5390 in FIGS. 53C and 53F,respectively, weather complication 5312 has been updated in accordancewith the time being scrubbed forward by 25 minutes to 11:34. Before thetime was scrubbed forward, weather complication 5312 displayed a currentweather temperature of 72°, while after the time has been scrubbedforward, weather complication 5312 has been updated to display aforecasted weather temperature of 73°, the forecasted weathertemperature being a forecast corresponding to the future scrubbing timeof 11:34.

In some embodiments, as a user scrubs forward and/or backward in time,one or more auditory and/or haptic outputs can optionally be provided toa user. In some embodiments, the auditory/haptic outputs can optionallybe one or more audible tones provided through a speaker, one or morevibrational outputs, one or more “clicking” haptic outputs, and/or oneor more spoken words or phrases provided through a speaker. In someembodiments, the auditory/haptic outputs can optionally indicate to auser that time-scrubbing mode is activated, that a scrubbing time ismoving forward or backward, and/or that one or more user interfaceobjects or complications has been updated in accordance with thescrubbing time.

In some embodiments, an auditory/haptic output can optionally beprovided to indicate that a scrubbing time has been updated inaccordance with a user's input. For example, as a user scrubs forward orbackward through time, a device can optionally provide anauditory/haptic output upon the scrubbing time being changed by apredefined amount of time, or upon the scrubbing time reaching apredefined time. For example, a device can optionally provide anauditory/haptic output as a user scrubs through time upon the scrubbingtime advancing (or retreating) by 1 minute, 15 minutes, one half hour,one hour, one day, one week, one month, and/or one year. A device canoptionally alternately or additionally provide an auditory/haptic outputas a user scrubs through time upon the scrubbing time changing minutes,15-minute intervals (e.g., 12:00, 12:15, 12:45, and so on), half-hourintervals, hours, days, weeks, months and/or years. In some embodiments,the number or frequency of auditory/haptic outputs can optionally bedynamically determined in accordance with the speed of a user'sscrubbing, such that a large number of such outputs are not provided inrapid succession when a user is scrubbing through time quickly.

In one example, as a user scrubs forward in time starting from 11:34,the device provides a first auditory/haptic “click” when the scrubbingtime reaches 12:00, and provides a second such auditory/haptic “click”when the scrubbing time reaches 1:00. In another example, the device canoptionally instead speak the scrubbing time as the user advances throughtime, such that the device would output “12 o'clock” and then “1o'clock” through a speaker.

In some embodiments, an auditory/haptic output can optionally beprovided to indicate that a complication or other user interface objecthas been updated in accordance with the scrubbing time. For example, asa user scrubs forward or backward through time and complications areupdated in accordance with the scrubbing time, a device can optionallyprovide an auditory/haptic output upon a complication being updated. Insome embodiments, the number or frequency of auditory/haptic outputs canoptionally be dynamically determined in accordance with the speed of auser's scrubbing, such that a large number of such outputs are notprovided in rapid succession when a user is scrubbing through timequickly.

In one example, as a user scrubs forward in time and a weathercomplication changes from indicating a current temperature to indicatinga forecasted temperature corresponding to a future scrubbing time, thedevice provides an auditory/haptic “click” when the complicationchanges. If the complication changes again as the user scrubs furtherforward in time, or backward in time, the device provides anotherauditory/haptic “click.” In another example, the device instead speakswords or phrases associated with the complication and/or with theupdated information indicated by the complication. For example, thedevice can optionally output “seventy-three degrees” when thecomplication is updated to indicate a forecasted temperature of 73°.

In some embodiments, a device can optionally provide one type ofauditory/haptic output as a user is actively scrubbing through time, andcan optionally provide another type of auditory/haptic output upondetecting that the user has ceased scrubbing and paused the scrubbingtime. For example, a device can optionally provide clickingauditory/haptic outputs as a user scrubs forward in time, indicating thehours as the scrubbing time advances past them and/or indicating changesto the complications as they are updated; then, when the user ceasesscrubbing forward and pauses the scrubbing time, the device canoptionally provide a spoken auditory output verbally describing thecurrent state of one or more complications, time indicators, and/orother user interface objects. Thus, a user can optionally be providedwith clicks as he scrubs through time, and then can optionally pause tobe provided with additional auditory spoken information about one ormore user interface objects at the scrubbing time upon which the userhas paused.

In some embodiments, auditory and/or haptic outputs can optionally beprovided during time scrubbing as part of an accessibility mode,screen-reader mode, and/or voiceover mode. Such modes can optionally beprovided to assist users who are blind or who have low vision in usingdevices. In some embodiments, a screen-reader mode can optionallyprovide auditory output, such as through a speaker, the output speakingsome or all of the contents of a displayed user interface. However, insome embodiments, speaking all of the contents of a user interface whilescrubbing through time is overly verbose and unwieldy, as many elementson the screen may be simultaneously and continuously changing, andauditory outputs would have to overlap or be delayed in time, makingthem unhelpful and/or unintelligible. To solve this problem, in someembodiments, a device can optionally provide haptic and/or auditoryfeedback with respect to only selected elements or user interfaceobjects. For example, in a screen-reader mode, a user can optionallyselect one user interface objects or complications as a “focus” of theinterface, for example by tapping the display at a locationcorresponding to the object or element, by swiping, or by actuating oneor more hardware buttons. While the user interface object is selected asthe “focus” and the user scrubs forward and/or backward in time, thedevice can optionally provide auditory and/or haptic outputs, in any ofthe manners discussed above, with respect only to the selected object.By providing auditory/haptic output with respect only to the respectedobject, the user may be able to more easily understand the output, as itcan optionally be provided by the device without overlapping with otheroutput or needing to be delayed in time.

At block 5424, optionally, the information corresponding to the firstnon-current time comprises projected data. In some embodiments, theinformation displayed by a user interface object or complication thathas been updated in a time-scrubbing mode can optionally includeprojected or forecasted information, such as a weather forecast. In someembodiments, when forecasted or projected information (rather than knownor scheduled information) is displayed, an indication (such as a visualsymbol, a display stylization, etc.) can optionally be provided to alertthe user that the information is a forecast or a projection. In theexample of interfaces 5360 and 5390 in FIGS. 53C and 53F, respectively,the information displayed by weather complication 5312 is projected datain the form of a forecasted weather prediction for a future time.

In some embodiments, forecasted or projected information can optionallypertain to a future scrubbing time, in that the prediction or forecastwas made about a future time, such that the user is provided with aforecast or a prediction for the future. In some embodiments, forecastedor projected information can optionally pertain to a past time, in thatthe prediction or forecast was made at a past time, such that the useris provided with a previous prediction or forecast.

At block 5426, optionally, the information corresponding to the firstnon-current time comprises a scheduled event. In some embodiments,information displayed by a complication can optionally include calendarinformation such as the name of a scheduled event, the time of ascheduled event, the place of a scheduled event, participants orinvitees to a scheduled event, or other information about a scheduledevent. For example, a complication can optionally be configured todisplay information from a user's personal calendar; in someembodiments, the complication can optionally display the name of acurrent calendar event, such as “Conference Call.” In some embodiments,the complication can optionally display the name of a nearest upcomingcalendar event. In some embodiments, when a user scrubs forward orbackward in time, such a calendar complication can optionally change todisplay information corresponding to a calendar event scheduled for thescrubbing time, or to display information corresponding to a nearestupcoming calendar event with respect to the scrubbing time.

In some embodiments, when scrubbing into the future and/or the past, thedevice can optionally determine what information to display in adifferent manner than the device determines what information to displayfor the current time when time-scrubbing mode is not activated. Forexample, if a meeting is scheduled for 12:00 noon, then a calendarcomplication can optionally, in some embodiments, display informationpertaining to the 12:00 noon meeting starting at a time before 12:00noon, such as 11:00 a.m. or 9:00 a.m., or whenever a previous calendarevent concludes. In this way, the user can optionally see the calendarevent regarding the 12:00 noon meeting before the time of the meeting,and is less likely to forget about the meeting and be late. Thus,information can optionally be displayed about the meeting for a periodof time that extends beyond (e.g., before) the time of the calendarevent in the user's calendar. In some embodiments, the same thing canoptionally not be true in time-scrubbing mode. For example, in someembodiments, when a user enters time-scrubbing mode, a calendarcomplication can optionally suppress display of information pertainingto calendar events when the scrubbing time is not set to a time forwhich the calendar event is actually scheduled. Thus, for a noonmeeting, despite the device displaying the meeting, in some embodiments,outside time-scrubbing mode when the current time is 11:09, display ofthe meeting can optionally be suppressed in time-scrubbing mode when thescrubbing time is set to 11:09. In some embodiments, suppressing displayof calendar events in time-scrubbing mode when the scrubbing time is notset to a time for which the calendar event is actually scheduled may aida user's quick comprehension of the time for which calendar events arescheduled when a user is scrubbing through time quickly. (Note that, inother embodiments, time-scrubbing mode can optionally display calendarinformation when the scrubbing time is not set to a time for which thecalendar event is scheduled; in some such embodiments, the device canoptionally display a time for the calendar event to aid a user'sunderstanding of the time of the calendar event as the user is scrubbingthrough time.)

At block 5428, optionally, the information corresponding to the firstnon-current time comprises historical data. In some embodiments,information displayed by a complication can optionally includehistorical information such as recorded data or other information.Recorded data or other information, in some embodiments, can optionallyinclude recorded measurements, figures, readings, statistics, or events.Recorded data or other information, in some embodiments, can optionallyinclude recorded forecasts or recorded predictions. Recorded data orother information, in some embodiments, can optionally include anyinformation regarding the previous state of a device and/or of a userinterface. In some embodiments, as a user scrubs through past times, adevice can optionally display historical data that pertains to the pastscrubbing time. In some embodiments, historical information canoptionally pertain to a past scrubbing time in that the informationitself concerns the past scrubbing time (e.g., a weather temperaturereading at the time). In some embodiments, historical information canoptionally pertain to a past scrubbing time in that the information wasrecorded or created at the past scrubbing time (e.g., a weather forecastmade at the past scrubbing time).

Block 5430 optionally follows from blocks 5416-5420. At block 5430,optionally, in response to detecting the first rotation of the rotatableinput mechanism, the device updates the first user interface object toindicate a lack of information corresponding to the first non-currenttime. In some embodiments, as a user is scrubbing forward or backward intime in a time-scrubbing mode, a user interface object or complicationcan optionally cease to be displayed to indicate that there is noinformation to be displayed corresponding to the selected scrubbingtime. For example, when a user scrubs a stock-market complication to afuture time, stock information may not be available for the future time;accordingly, the complication (or part of the complication) canoptionally cease to be displayed. A similar result could occur when auser scrubs so far forward in time that reliable projection or forecastdata is not available; for example, a user may scrub so far into thefuture that no weather forecast is available, and a weather complicationcould cease to be displayed. A similar result could occur when a userscrubs so far backward in time that historical data is no longeravailable; for example, a device (or an information source to which thedevice has access) can optionally only cache or otherwise store alimited amount of historical information, and when a user scrubs beyondthat point, a complication can optionally cease to be displayed. Asimilar result could also occur when a user scrubs to a time to which nocalendar data applies; for example, if a user scrubs to a time at whichno events are scheduled on a calendar, then a device can optionallycease to display a calendar complication.

In some embodiments, when a user scrubs to a time for which no relevantinformation is available for display by a complication, a complicationcan optionally fade to a translucent appearance, can optionally bedisplayed in a faded or muted color scheme, or can optionally bedisplayed in a grayed-out color scheme, to indicate to the user that noinformation is available for the selected scrubbing time. In some suchembodiments, the complication can optionally continue to display, in thealtered (e.g., faded or grayed-out) manner, the information that wasmost recently displayed by the complication. This may help the user toknow that information pertaining to the selected scrubbing time is notavailable, while allowing the user to remain oriented to, and aware of,the complication's presence.

In FIG. 54C, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism. In FIG. 54C, block 5414 is continued, suchthat blocks 5432-5442 (some of which are optional) are performed “inresponse to detecting the first rotation of the rotatable inputmechanism.” In discussing blocks 5432 to 5442 below, the phrase “inresponse to detecting the first rotation of the rotatable inputmechanism” may or may not be repeated for clarity.

Block 5432 follows from blocks 5422-5428, or optionally from block 5430.At block 5432, in response to detecting the first rotation of therotatable input mechanism, the device displays one of the firstcurrent-time indicator and a second current-time indicator. In someembodiments, block 5432 can optionally be performed in response todetecting a user input that activates a time-scrubbing mode, such as theuser input detected at block 5408. In some embodiments, when atime-scrubbing mode is activated (whether by a touch contact detected ona touch-sensitive surface or by a rotation of a rotatable inputmechanism), in addition to displaying a non-current-time indicatorindicating a scrubbing time, the device can optionally also display acurrent-time indicator. In some embodiments, the current-time indicatordisplayed in time-scrubbing mode can optionally be the same current-timeindicator that was displayed before the activation of time-scrubbingmode, such as the current-time indicator displayed at block 5404, suchthat the same current-time indicator continues to be displayed. In someembodiments, the current-time indicator displayed in time-scrubbing modecan optionally be a second current-time indicator different from thecurrent-time indicator that was displayed before the activation oftime-scrubbing mode.

At block 5434, optionally, displaying the first current-time indicatorin response to detecting the first rotation comprises displaying thefirst current-time indicator with a modified visual appearance. In someembodiments, upon the activation of time-scrubbing mode, the visualappearance of the first current-time indicator can optionally be alteredin such a way so as to signal to the user that time-scrubbing mode hasbeen activated and to direct the user's focus to the non-current-timeindicator rather than the current-time indicator. For example, a size,shape, color, highlighting, and/or animation style of a current-timeindicator can optionally be altered upon the activation oftime-scrubbing mode.

In some embodiments, a current-time indicator can optionally bedisplayed in a faded, muted, partially transparent, or grayed-out colorscheme while time-scrubbing mode is active. In the depicted example ofinterface 5360 in FIG. 53C, clock hands 5310 a and 5310 b are displayedin a grayed-out color scheme, as indicated by the hashing shown in thefigure. This grayed-out color scheme can optionally signal to a userthat time-scrubbing mode is active, and can optionally direct a user'sattention to scrubbing hands 5322 a and 5322 b instead, which canoptionally be displayed in a brighter or more noticeable color, such asgreen.

In the example of interface 5380 in FIG. 53E, digital clock face 5328can optionally be displayed in green when time-scrubbing mode isactivated, whereas it can optionally have been displayed in white beforetime-scrubbing mode was activated. In some embodiments, displaying moreuser interface objects, including current-time indicators, in a brightcolor such as green can optionally signal to a user that the device isin a time-scrubbing mode of operation.

In some embodiments, a current-time indicator can optionally bedisplayed in a smaller size than it was displayed before the activationof a time-scrubbing mode. In the depicted example of interface 5380 inFIG. 53E, digital clock face 5328 has been translated to the top cornerof display 5302 (as indicated by the diagonal arrow) and is displayed ina smaller size than the size at which it was displayed (in interface5370 in FIG. 53D) before the activation of time-scrubbing mode. Thesmaller display size of the current-time indicator can optionally signalto a user that time-scrubbing mode is active, and can optionally directa user's attention to digital clock face 5332, which can optionally bedisplayed in a larger size and can optionally display a scrubbing time.

At block 5436, optionally, displaying the first current-time indicatorin response to detecting the first rotation comprises displaying thefirst current-time indicator in a different position on the display thana position at which it was displayed prior to detecting the firstrotation. In some embodiments, upon the activation of time-scrubbingmode, a current-time indicator can optionally cease to be displayed inone position and instead be displayed in another position. The positionat which the current-time indicator is displayed during time-scrubbingmode can optionally be a less prominent position than the priorposition, such as a position closer to an edge or corner of the display.In the example of interface 5390 in FIG. 53F, digital clock face 5328 isdisplayed at a different position than the position at which it wasdisplayed (in interface 5370 in FIG. 53D) prior to the activation oftime-scrubbing mode, having been moved closer to the upper right-handcorner of display 5302.

At block 5438, optionally, displaying the first current-time indicatorin response to detecting the first rotation comprises animating thefirst current-time indicator from its initial position to the differentposition on the display. In some embodiments, the animation canoptionally comprise the indicator fading away (e.g., becoming moretransparent) from its old position and/or fading into (e.g., becomingless transparent) its new position. In some embodiments, the animationcan optionally include translating the object across the display. Insome embodiments, the animation can optionally include displaying theobject increasing or decreasing in size. In some embodiments, theanimation can optionally include any of the animations described abovewith respect to digital clock face 5317 and FIG. 53C or with respect toblock 5422. In some embodiments, the current-time indicator canoptionally suddenly cease to be displayed at its initial position andimmediately begin to be displayed at the different position.

At block 5440, optionally, in response to detecting the first rotationof the rotatable input mechanism, the device displays a time differenceindicator indicating a time difference between the current time and thefirst non-current time. In some embodiments, a time difference indicatorcan optionally be any user interface object that indicates a differencebetween one time and another time, such as the difference between acurrent time and a scrubbing time. In some embodiments, a timedifference indicator can optionally indicate a number of seconds,minutes, hours, days, weeks, months, years, etc. In some embodiments, atime difference indicator can optionally indicate whether a scrubbingtime is in the future or in the past relative to a current time. In someembodiments, a time difference indicator is automatically displayed uponactivation of time-scrubbing mode. In some embodiments, explicitlydisplaying the difference between the scrubbing time and the currenttime may help a user to more easily understand and contextualize how faraway from the current time the scrubbing time (and the correspondinginformation displayed in the complications) is. In the example ofinterfaces 5350 and 5360 in FIGS. 53B and 53C, respectively, timedifference indicator 5318 uses numerals to indicate the number ofminutes difference between the current time and the scrubbing time,which is zero minutes in FIG. 53B and 25 minutes in FIG. 53C. In theexample depicted, time difference indicator 5318 uses a “+” symbol toindicate that the scrubbing time is in the future as compared to thecurrent time (and defaults to using a “+” symbol when the scrubbing timeis equal to the current time). In some embodiments, if the scrubbingtime is in the past as compared to the current time, then timedifference indicator 5318 can optionally display a “−” symbol toindicate that the scrubbing time is a past time.

In some embodiments, when time-scrubbing mode is activated, elementspreviously displayed on the display can optionally be removed from thedisplay. For example, in some embodiments, complications or other userinterface objects displayed at a portion of the display where a timedifference indicator is displayed can optionally be removed from thedisplay (e.g., the device can optionally cease to display them) duringtime-scrubbing mode. In some embodiments, the same can optionally betrue of interface objects or complications that are displayed at alocation on the display where a current-time indicator (or anaccompanying object such as the displayed word “NOW”) is displayed whentime-scrubbing mode is active. In some embodiments, complications canoptionally be removed from the display upon the activation oftime-scrubbing mode without regard for whether any other object will bedisplayed at the same location on the display during time-scrubbingmode. In some embodiments, when a current-time indicator or atime-difference indicator is displayed at or moved to a location of adisplay at which numbers on a likeness of an analog clock face weredisplayed, the numbers on the likeness of the analog clock face canoptionally be hidden; for example, if a current-time indicator ortime-difference indicator is displayed near the bottom of a clockinterface in a time-scrubbing mode, then the numbers “5,” “6,” and “7”can optionally be hidden on the clock face. In some embodiments, dialsor sub-dials displayed in a device interface (such as any dial describedelsewhere in this disclosure) can optionally cease to be displayed uponthe activation of time-scrubbing mode when a time-difference indicatoror a current-time indicator is displayed at a portion of the display atwhich the dial or sub-dial was previously displayed.

In some embodiments, user interface elements displayed before theactivation of a time-scrubbing mode can optionally change in size orappearance in order to make room for the display of a time-differenceindicator or a current-time indicator in time-scrubbing mode. Forexample, in some embodiments, previously-displayed tick marks canoptionally be replaced by or animated as transitioning into dots, whichcan optionally be smaller in size and/or can optionally have more emptyspace between them on the display. In some embodiments, any suitableuser interface object can optionally shrink in size and/or changelocations on the display upon the activation of time-scrubbing mode,including to create space on the display for the display of atime-difference indicator and/or a current-time indicator or associateduser interface objects.

In FIG. 54D, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism.

Blocks 5442, 5444-5446, and 5448 each follow, optionally, from blocks5414-5440.

At block 5442, optionally, in response to a passage of time, the deviceupdates the non-current-time indicator to indicate a second non-currenttime in accordance with the passage of time, such that a time differencebetween the current time and a presently indicated non-current timeremains fixed. In some embodiments, as time passes, the current time isaccordingly updated to keep time. Additionally to updating the currenttime, the device, in some embodiments, also updates a non-current time,such as a scrubbing time for time-scrubbing mode, in accordance with thepassage of time. In this way, in some embodiments, once a user has set ascrubbing time, the difference between the scrubbing time and thecurrent time can optionally remain fixed even as time passes. Thus, insome embodiments, when a scrubbing time is set to the future, thecurrent time will not “catch up” to the scrubbing time, because thescrubbing time will advance in time in parallel to the current time.

In some embodiments, as the scrubbing time is advanced in accordancewith the passage of time, complications and other user interface objectscan optionally be accordingly updated, in accordance with any of themethods explained above, to reflect the newly updated scrubbing time.Thus, a complication in time-scrubbing mode can optionally be updated,in some embodiments, both in accordance with the scrubbing time beingaltered by user input and in accordance with the scrubbing time beingaltered by the passage of time.

At block 5444, optionally, while displaying the updated first userinterface object displaying information corresponding to the firstnon-current time, the device detects a second touch contact at alocation corresponding to the updated first user interface object, andin response to detecting the second touch contact, displays a userinterface corresponding to the first user interface object. The touchcontact detected can optionally be a single-touch input, a multi-touchinput, a single-tap input, and/or a multi-tap input detected by touch-and/or pressure-sensitive elements in any touch- and/orpressure-sensitive surface, including a touch-screen. In someembodiments, complications or other user interface objects that areupdated in accordance with a scrubbing time in time-scrubbing mode canoptionally be selectable affordances, such that if a device detects aninput at a location corresponding to the complication, then an interfaceor application associated with the complication can optionally beaccessed. For example, a user can optionally tap on a weathercomplication, in some embodiments, such as weather complication 5312, tocause an associated weather application to be opened. In anotherexample, a user can optionally tap on a stock-market complication suchas stock-market complication 5314, and, in some embodiments, astock-market application can optionally be opened. In the depictedexample of FIGS. 53C and 53F, user inputs 5336 a and 5336 b are detectedon display 5302 at a location at which weather complication 5312 isdisplayed; in some embodiments, in response to detecting user input 5336a or 5336 b, a weather application can optionally be accessed and aweather interface can optionally be displayed.

At block 5446, optionally, the user interface displayed in accordancewith the detection of a second touch contact at a location correspondingto the updated first user interface object corresponds to the firstnon-current time. In some embodiments, the functionality of tapping orotherwise selecting complications or other user interface objects canoptionally vary in accordance with the displayed scrubbing time, suchthat a different application or interface can optionally be provideddepending on what the scrubbing time is set to at the moment of theuser's selection. For example, in response to a user tapping a weathercomplication when the device is scrubbed to a past time, an interface ofa weather application showing historical weather data for thescrubbed-to past time can optionally be displayed; in response to a usertapping a weather complication when the device is scrubbed to a futuretime, an interface of a weather application showing forecasted weatherfor the scrubbed-to future time can optionally be displayed. In anotherexample, in response to a user tapping a calendar complication, acalendar event that is scheduled for the scrubbed-to time can optionallybe opened, and an interface for that specific event can optionally bedisplayed. In the depicted example of FIGS. 53C and 53F, in response todetecting user input 5336 a or 5336 b, device 5300 can optionallyprovide an interface corresponding to forecasted weather informationassociated with the scrubbing time of 11:34 in some embodiments.

In some embodiments, a displayed complication can optionally correspondto an interface of the device that is configured to display a likenessof the Earth, the moon, and/or the solar system. In some embodiments, ifa user scrubs time forward or backward on a scrubbing interface thatcontains such a complication, and then taps the complication to selectit, then a corresponding Earth, moon, and/or solar system interface canoptionally be displayed, wherein the Earth, moon, and/or solar systeminterface is itself scrubbed forward to the scrubbing time of theprevious interface. In some embodiments, a user can optionally selectcomplications corresponding to Earth, moon, and/or solar systeminterfaces to cause an animation to be displayed of the interface“flying” (e.g., smoothly zooming and panning) between views of theEarth, views of the moon, and/or views of the solar system. As the userflies between these various interfaces, in some embodiments, timescrubbing can optionally be maintained, and the scrubbing time canoptionally be reflected in the complications displayed in each interfaceand/or in the displayed likenesses of the Earth, the moon, and/or thesolar system.

At block 5448, optionally, the device detects a third touch contact at alocation corresponding to the first current-time indicator, and inresponse to detecting the third touch contact, ceases to display thenon-current-time indicator and updates the first user interface objectto display information corresponding to the current time. The touchcontact detected can optionally be a single-touch input, a multi-touchinput, a single-tap input, and/or a multi-tap input detected by touch-and/or pressure-sensitive elements in any touch- and/orpressure-sensitive surface, including a touch-screen. In someembodiments, when a user taps on the current-time indicator, the devicecan optionally responsively exit time-scrubbing mode. Upon exitingtime-scrubbing mode, in some embodiments, the device can optionallycease to display the scrubbing time. Upon exiting time-scrubbing mode,in some embodiments, display of the current time can optionally returnto an original visual appearance (e.g., position, size, color, style,etc.) that was displayed before time-scrubbing mode was activated. Uponexiting time-scrubbing mode, in some embodiments, complications or otheruser interface object that were updated, in accordance with any of theabove methods, to correspond to a scrubbing time, can optionally beagain updated to correspond to the current time. In some embodiments,this can optionally involve returning to their original appearance frombefore time-scrubbing mode was activated, while in some embodiments itcan optionally involve displaying new and/or different information (suchas information corresponding to a new current time that is differentfrom when time-scrubbing mode was activated, or information that isnewly available or has been updated since time-scrubbing mode wasactivated). The displayed complications or user interface objects canoptionally be updated, upon deactivating time-scrubbing mode, inaccordance with any of the animations discussed above with reference todigital clock face 5317 in FIG. 53C. In the depicted example of FIGS.53C and 53F, touch contacts 5324 a and 5334 a are each detected at alocation on display 5302 at which a current-time indicator is displayed;in response to detecting either input, device 5300 can optionally causetime-scrubbing mode to be deactivated, and the displayed time indicatorsand complications can optionally be accordingly updated. In the depictedexample, if no information has changed and the time has not changedsince the activation of time-scrubbing mode, exiting time-scrubbing modein FIGS. 53C and 53F can optionally cause the display, respectively, ofinterface 5340 in FIG. 53A and of interface 5370 in FIG. 53C.

In some embodiments, other user inputs can optionally be operable tocause the device to exit a time-scrubbing mode. In some embodiments,alternate user inputs that can optionally cause a device to exit atime-scrubbing mode can optionally include a depression of a rotatableand depressible input mechanism, such as user inputs 5324 b and 5334 bin FIGS. 53C and 53F, respectively. Allowing a user to exit atime-scrubbing mode by depressing a rotatable and depressible inputmechanism can optionally increase the ease of scrubbing time forward orbackward and then easily exiting time-scrubbing mode when a user isfinished with time-scrubbing mode, as commands to execute both functionscan be entered with a single input mechanism. In some embodiments, adevice can optionally exit a time-scrubbing mode after a predefinedperiod of time of inactivity, such as when a device times out and adisplay is darkened.

At block 5450, optionally, the device detects a second rotation of therotatable input mechanism, and, in response to detecting the secondrotation of the rotatable input mechanism, the device updates thenon-current-time indicator to indicate a third non-current time,determined in accordance with the second rotation, and updates the firstuser interface object to display information corresponding to the thirdnon-current time, wherein the information corresponding to the thirdnon-current time pertains to the first information source and isinformation other than a day, a time, or a date of the first non-currenttime; and displays one of the first current-time indicator and thesecond current-time indicator. In some embodiments, after detecting afirst rotation and setting a first scrubbing time, as described above, adevice can optionally then detect another rotation of the samerotational input mechanism, and can optionally set another scrubbingtime in accordance with the second rotation. The device can optionallyset a second scrubbing time in accordance with any of the methodsdescribed above, and can optionally update the displayed user interfaceobject and complications to correspond to the second scrubbing time inaccordance with any of the methods described above. In some embodiments,a user can optionally scrub forward or backward in time, pause, and thenscrub forward or backward in time again, with or without leavingtime-scrubbing mode. In some embodiments, displayed complications canoptionally be dynamically updated throughout the process to alwaysreflect the displayed scrubbing time as the user scrubs, pauses, andthen scrubs again. In some embodiments, this process can optionally bewholly or partially repeated or iterated any number of times.

In FIG. 54E, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism.

Blocks 5452 and 5454 follow, optionally, from blocks 5414-5440.

At block 5452, optionally, the device displays a second user interfaceobject configured to display second information corresponding to thecurrent time, wherein the second information corresponding to thecurrent time pertains to a second information source and is informationother than a day, time, or date of the current time; and, in response todetecting the first rotation of the rotatable input mechanism: updatesthe second user interface object to display second informationcorresponding to the first non-current time, wherein the secondinformation corresponding to the first non-current time pertains to thesecond information source and is information other than a day, time, ordate of the first non-current time.

At block 5454, optionally, the first and second information sources areseparate applications.

In some embodiments, a device can optionally display more than onecomplication or other user interface object, wherein the complicationsor other user interface objects pertain to separate subject matters,separate information sources, or separate applications of the device.For example, in some embodiments, an interface of a device such as awatch face interface or a home screen interface can optionally displaytwo distinct complications, each complication being associated with adistinct application of the device and each complication drawinginformation from the respective associated application and displayingthe information on the interface. In the depicted example of FIG. 53A,weather complication 5312 and stock-market complication 5314 aredistinct complications that can optionally each be associated with adistinct information source and/or application (e.g., a weatherapplication and a stock-market complication, respectively).

In some embodiments, when a user scrubs time forward or backward in anyof the manners described above, not just one but both (and, in someembodiments, more than two) of the displayed complications or other userinterface objects are simultaneously updated in accordance with the timescrubbing. A second displayed complication or user interface object (inaddition to a third, fourth, etc.) can optionally be updated inaccordance with scrubbing by any of the methods described above. In someembodiments, all of the complications displayed on an interface canoptionally be simultaneously updated in accordance with the displayednon-current time as a user scrubs through time. This may be advantageousbecause, in some embodiments, a user may be able to observe pastinformation and/or future information of more than one informationsource or of more than one application without having to separately openeach application; this may allow a user to observe and recognizecontextual relationships between temporally-related data provided bydifferent applications or different information sources by being able tosee information from all applications at once, the information displayedall corresponding to the same past time or to the same future time.

In the depicted example of FIG. 53C, in response to the user scrubbingforward in time by 25 minutes to a scrubbing time of 11:34, weathercomplication 5312 has been updated in accordance with the scrubbing timeto display a forecasted weather temperature of 73° for the scrubbingtime of 11:34. At the same time, stock-market complication 5314 has beenupdated by being removed from interface 5360, in accordance with thefact that no information is available from the stock-market applicationor information source associated with stock-market complication 5314.(In some embodiments, a second complication having access toinformation, from an associated application or information source,corresponding to the scrubbing time of 11:34, could display theinformation alongside the information displayed by weather complication5312.) Thus, in some embodiments, in order to view future information(or to be informed of a lack of future information) from the distinctand separate applications that are associated with complications 5312and 5314, a user may not need to separately access each application orseparately instruct each application to access and/or display futureinformation; rather, simply by scrubbing to a future time, bothcomplications can optionally be caused to simultaneously access anddisplay future information corresponding to the selected scrubbing time.

It should be understood that the particular order in which theoperations in FIG. 54 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.

Note that details of the processes described above with respect tomethod 5400 (e.g., FIG. 54) are also applicable in an analogous mannerto the methods and techniques described elsewhere in this application.For example, other methods described in this application can optionallyinclude one or more of the characteristics of method 5400. For example,the devices, hardware elements, inputs, interfaces, modes of operation,faces, time indicators, and complications described above with respectto method 5400 can optionally share one or more of the characteristicsof the devices, hardware elements, inputs, interfaces, modes ofoperation, faces, time indicators, and complications described elsewherein this application with respect to other methods. Moreover, thetechniques described above with respect to method 5400 can optionally beused in combination with any of the interfaces, faces, or complicationsdescribed elsewhere in this application. For brevity, these details arenot repeated elsewhere in this application.

In accordance with some embodiments, FIG. 55 shows an exemplaryfunctional block diagram of an electronic device 5500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5500 are configured to perform the techniques described above.The functional blocks of the device 5500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 55 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 55, electronic device 5500 includes a display unit 5502configured to display a graphic user interface including complications,current-time indicators, and non-current-time indicators; electronicdevice 5500 further includes a rotatable input mechanism unit 5504configured to receive rotational inputs. Optionally, device 5500 alsoincludes a touch-sensitive surface unit 5506 configured to receivecontacts. Device 5500 further includes processing unit 5508 coupled todisplay unit 5502, rotatable input mechanism unit 5504, and, optionally,touch-sensitive surface unit 5506. Processing unit 5508 contains displayenabling unit 5510, detecting unit 5512, and updating unit 5514.Optionally, processing unit 5508 further ceasing display enabling unit5516.

Processing unit 5512 is configured to: enable display (e.g., withdisplay enabling unit 5510) on display unit 5502 of a first current-timeindicator indicating a current time; enable display (e.g., with displayenabling unit 5510) on display unit 5502 of a first user interfaceobject configured to display information corresponding to the currenttime, wherein the information corresponding to the current time pertainsto a first information source and is information other than a day, time,or date of the current time; detect (e.g., with detecting unit 5512) afirst rotation of rotatable input mechanism unit 5504; in response todetecting the first rotation of rotatable input mechanism unit 5504:enable display (e.g., with display enabling unit 5510) on display unit5502 of a non-current-time indicator indicating a first non-current timedetermined in accordance with the first rotation; update (e.g., withupdating unit 5514) the first user interface object to displayinformation corresponding to the first non-current time, wherein theinformation corresponding to the first non-current time pertains to thefirst information source and is information other than a day, time, ordate of the first non-current time; and enable display (e.g., withdisplay enabling unit 5510) on display unit 5502 of one of the firstcurrent-time indicator and a second current-time indicator.

In some embodiments, processing unit 5508 is further configured to: inresponse to detecting the first rotation of the rotatable inputmechanism unit 5504: update (e.g., with updating unit 5514) the firstuser interface object to indicate a lack of information corresponding tothe first non-current time.

In some embodiments, the first non-current time is a future time.

In some embodiments, the information corresponding to the firstnon-current time comprises projected data.

In some embodiments, the information corresponding to the firstnon-current time comprises a scheduled event.

In some embodiments, the first non-current time is a past time.

In some embodiments, the information corresponding to the firstnon-current time comprises historical data.

In some embodiments, enabling display (e.g., with display enabling unit5510) on display unit 5502 of the first current-time indicator inresponse to detecting the first rotation comprises enabling display ondisplay unit 5502 of the first current-time indicator with a modifiedvisual appearance.

In some embodiments, enabling display (e.g., with display enabling unit5510) on display unit 5502 of the first current-time indicator inresponse to detecting the first rotation comprises enabling display ondisplay unit 5502 of the first current-time indicator in a differentposition on the display than a position at which it was displayed priorto detecting the first rotation.

In some embodiments, enabling display (e.g., with display enabling unit5510) on display unit 5502 of the first current-time indicator inresponse to detecting the first rotation comprises animating the firstcurrent-time indicator from its initial position to the differentposition on the display.

In some embodiments, the non-current-time indicator is displayed at alocation at which the first current-time indicator was displayed beforethe detection of the first rotation of rotatable input mechanism unit5504.

In some embodiments, processing unit 5508 is further configured to: inresponse to detecting the first rotation of rotatable input mechanismunit 5504, enable display (e.g., with display enabling unit 5510) ondisplay unit 5502 of a time difference indicator indicating a timedifference between the current time and the first non-current time.

In some embodiments, processing unit 5508 is further configured to:before detecting the first rotation of rotatable input mechanism unit5504, detect (e.g., with detecting unit 5512) a first touch contact at alocation corresponding to the first current-time indicator; and inresponse to detecting the first touch contact: enable display (e.g.,with display enabling unit 5510) on display unit 5502 of thenon-current-time indicator indicating the current time.

In some embodiments, processing unit 5508 is further configured to: inresponse to a passage of time, update (e.g., with updating unit 5514)the non-current-time indicator to indicate a second non-current time inaccordance with the passage of time, such that a time difference betweenthe current time and a presently indicated non-current time remainsfixed.

In some embodiments, processing unit 5508 is further configured to:while enabling display on display unit 5502 of the updated first userinterface object displaying information corresponding to the firstnon-current time, detect (e.g., with detecting unit 5512) a second touchcontact at a location corresponding to the updated first user interfaceobject; and in response to detecting the second touch contact, enabledisplay (e.g., with display enabling unit 5510) on display unit 5502 ofa user interface corresponding to the first user interface object.

In some embodiments, the user interface corresponds to the firstnon-current time.

In some embodiments, processing unit 5508 is further configured to:after detecting the first rotation of rotatable input mechanism unit5504, detect (e.g., with detecting unit 5512) a third touch contact at alocation corresponding to the first current-time indicator; and inresponse to detecting the third touch contact: cease to enable display(e.g., with ceasing display enabling unit 5518) on display unit 5502 ofthe non-current-time indicator; and update (e.g., with updating unit5514) the first user interface object to display informationcorresponding to the current time.

In some embodiments, processing unit 5508 is further configured to:detect (e.g., with detecting unit 5512) a second rotation of rotatableinput mechanism unit 5504; in response to detecting the second rotationof rotatable input mechanism unit 5504: update (e.g., with updating unit5514) the non-current-time indicator to indicate a third non-currenttime determined in accordance with the second rotation; update (e.g.,with updating unit 5514) the first user interface object to displayinformation corresponding to the third non-current time, wherein theinformation corresponding to the third non-current time pertains to thefirst information source and is information other than a day, time, ordate of the first non-current time; and enable display (e.g., withdisplay enabling unit 5510) on display unit 5502 of one of the firstcurrent-time indicator and the second current-time indicator.

In some embodiments, processing unit 5508 is further configured to:enable display (e.g., with display enabling unit 5510) on display unit5502 of a second user interface object configured to display secondinformation corresponding to the current time, wherein the secondinformation corresponding to the current time pertains to a secondinformation source and is information other than a day, time, or date ofthe current time; and in response to detecting the first rotation ofrotatable input mechanism unit 5504: update (e.g., with updating unit5514) the second user interface object to display second informationcorresponding to the first non-current time, wherein the secondinformation corresponding to the first non-current time pertains to thesecond information source and is information other than a day, time, ordate of the first non-current time.

In some embodiments, the first and second information sources areseparate applications.

The operations described above with reference to FIGS. 54A-54E are,optionally, implemented by components depicted in FIG. 1A, 1B, 2, 3, 4A,4B, 5A, 5B, 53A, 53B or 55. For example, displaying operations 5404,5406, 5416, and 5432; detecting operation 5412; and updating operation5422 may be implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by a portable multifunction devicewith a display and a physical rotatable input mechanism that rotatesrelative to a housing of the device, cause the device to: display afirst user interface on the display that includes concurrentlydisplaying: a first current-time indicator indicating a current time;and a first user interface object configured to display informationcorresponding to the current tune, wherein the information correspondingto the current time pertains to a first information source and isinformation other than a day, time, or date of the current time; whiledisplaying the first user interface on the display, detect a firstrotation of the physical rotatable input mechanism relative to thehousing of the device; in response to detecting the first rotation ofthe physical rotatable input mechanism, update the first user interfaceto include: a non-current-time indicator indicating a first non-currenttime determined in accordance with the first rotation; informationcorresponding to the first non-current time displayed at a location atwhich the first user interface object was displayed prior to detectingthe first rotation, wherein the information corresponding to the firstnon-current time pertains to the first information source and isinformation other than a day, time, or date of the first non-currenttime; and a representation of the current time, wherein therepresentation of the current time indicates the current time; whiledisplaying the updated first user interface, detect a first touchcontact on the display; and in response to detecting the first touchcontact on the display: in accordance with a determination that thefirst touch contact is at a location corresponding to the informationcorresponding to the first non-current time displayed at a location atwhich the first user interface object was displayed prior to detectingthe first rotation: display a second user interface corresponding to thefirst user interface object, wherein the second user interface is basedat least in part on the information corresponding to the firstnon-current time; and in accordance with a determination that the firsttouch contact is at a location corresponding to the representation ofthe current time that is displayed concurrently with the non-currenttime indicator that was displayed in response to detecting the firstrotation of the physical rotatable input mechanism, update the firstuser interface to: cease to display the non-current-time indicator thatwas displayed in response to detecting the first rotation of thephysical rotatable input mechanism; and display informationcorresponding to the current time at a location at which the first userinterface object was displayed prior to detecting the first rotation. 2.The non-transitory computer-readable storage medium of claim 1, whereinthe instructions further cause the device to: in response to detectingthe first rotation of the physical rotatable input mechanism relative tothe housing of the device, update the first user interface to indicate alack of information corresponding to the first non-current time.
 3. Thenon-transitory computer-readable storage medium of claim 1, wherein thefirst non-current time is a future time.
 4. The non-transitorycomputer-readable storage medium of claim 3, wherein the informationcorresponding to the first non-current time comprises projected data. 5.The non-transitory computer-readable storage medium of claim 3, whereinthe information corresponding to the first non-current time comprises ascheduled event.
 6. The non-transitory computer-readable storage mediumof claim 1, wherein the first non-current time is a past time.
 7. Thenon-transitory computer-readable storage medium of claim 6, wherein theinformation corresponding to the first non-current time compriseshistorical data.
 8. The non-transitory computer-readable storage mediumof claim 1, wherein updating the first user interface to include therepresentation of the current time in response to detecting the firstrotation comprises displaying the first current-time indicator with amodified visual appearance.
 9. The non-transitory computer-readablestorage medium of claim 1, wherein updating the first user interface toinclude the representation of the current time in response to detectingthe first rotation comprises displaying the first current-time indicatorin a different position on the display than a position at which it wasdisplayed prior to detecting the first rotation.
 10. The non-transitorycomputer-readable storage medium of claim 9, wherein updating the firstuser interface to include the representation of the current time inresponse to detecting the first rotation comprises animating the firstcurrent-time indicator from its initial position to the differentposition on the display.
 11. The non-transitory computer-readablestorage medium of claim 1, wherein the non-current-time indicator isdisplayed at a location at which the first current-time indicator wasdisplayed before the detection of the first rotation of the physicalrotatable input mechanism.
 12. The non-transitory computer-readablestorage medium of claim 1, wherein the instructions further cause thedevice to: in response to detecting the first rotation of the physicalrotatable input mechanism relative to the housing of the device, updatethe first user interface to include a time difference indicatorindicating a time difference between the current time and the firstnon-current time.
 13. The non-transitory computer-readable storagemedium of claim 1, wherein the instructions further cause the device to:in response to a passage of time, update the non-current-time indicatorto indicate a second non-current time in accordance with the passage oftime, such that a time difference between the current time and apresently indicated non-current time remains fixed.
 14. Thenon-transitory computer-readable storage medium of claim 1, wherein theinstructions further cause the device to: detect a second rotation ofthe physical rotatable input mechanism relative to the housing of thedevice; in response to detecting the second rotation of the physicalrotatable input mechanism, update the first user interface to include:the non-current-time indicator updated to indicate a third non-currenttime determined in accordance with the second rotation; informationcorresponding to the third non-current time displayed at a location atwhich the first user interface object was displayed prior to detectingthe second rotation, wherein the information corresponding to the thirdnon-current time pertains to the first information source and isinformation other than a day, time, or date of the first non-currenttime; and the representation of the current time.
 15. The non-transitorycomputer-readable storage medium of claim 1, wherein displaying thefirst user interface on the display includes concurrently displaying:the first current-time indicator indicating a current time; the firstuser interface object configured to display information corresponding tothe current time; and a second user interface object configured todisplay second information corresponding to the current time, whereinthe second information corresponding to the current time pertains to asecond information source and is information other than a day, time, ordate of the current time; and wherein the instructions further cause thedevice to: in response to detecting the first rotation of the physicalrotatable input mechanism, update the first user interface to include:second information corresponding to the first non-current time displayedat a location at which the second user interface object was displayedprior to detecting the first rotation, wherein the second informationcorresponding to the first non-current time pertains to the secondinformation source and is information other than a day, time, or date ofthe first non-current time.
 16. The non-transitory computer-readablestorage medium of claim 15, wherein the first and second informationsources are separate applications.
 17. A method, comprising: at anelectronic device with a display and a physical rotatable inputmechanism that rotates relative to a housing of the device: displaying afirst user interface on the display that includes concurrentlydisplaying: a first current-time indicator indicating a current time;and a first user interface object configured to display informationcorresponding to the current time; wherein the information correspondingto the current time pertains to a first information source and isinformation other than a day, time, or date of the current time; whiledisplaying the first user interface on the display, detecting a firstrotation of the physical rotatable input mechanism relative to thehousing of the device; in response to detecting the first rotation ofthe physical rotatable input mechanism; updating the first userinterface to include: a non-current-time indicator indicating a firstnon-current time determined in accordance with the first rotation;information corresponding to the first non-current time displayed at alocation at which the first user interface object was displayed prior todetecting the first rotation, wherein the information corresponding tothe first non-current time pertains to the first information source andis information other than a day, time, or date of the first non-currenttime; and a representation of the current time, wherein therepresentation of the current time indicates the current time; whiledisplaying the updated first user interface, detecting a first touchcontact on the display; and in response to detecting the first touchcontact on the display: in accordance with a determination that thefirst touch contact is at a location corresponding to the informationcorresponding to the first non-current time displayed at a location atwhich the first user interface object was displayed prior to detectingthe first rotation: displaying a second user interface corresponding tothe first user interface object, wherein the second user interface isbased at least in part on the information corresponding to the firstnon-current time; and in accordance with a determination that the firsttouch contact is at a location corresponding to the representation ofthe current time that is displayed concurrently with the non-currenttime indicator that was displayed in response to detecting the firstrotation of the physical rotatable input mechanism, updating the firstuser interface by: ceasing to display the non-current-time indicatorthat was displayed in response to detecting the first rotation of thephysical rotatable input mechanism; and displaying informationcorresponding to the current time at a location at which the first userinterface object was displayed prior to detecting the first rotation.18. The method of claim 17, further comprising: in response to detectingthe first rotation of the physical rotatable input mechanism relative tothe housing of the device, updating the first user interface to indicatea lack of information corresponding to the first non-current time. 19.The method of claim 17, wherein the first non-current time is a futuretime.
 20. The method of claim 19, wherein the information correspondingto the first non-current time comprises projected data.
 21. The methodof claim 19, wherein the information corresponding to the firstnon-current time comprises a scheduled event.
 22. The method of claim17, wherein the first non-current time is a past time.
 23. The method ofclaim 22, wherein the information corresponding to the first non-currenttime comprises historical data.
 24. The method of claim 17, whereinupdating the first user interface to include the representation of thecurrent time in response to detecting the first rotation comprisesdisplaying the first current-time indicator with a modified visualappearance.
 25. The method of claim 17, wherein updating the first userinterface to include the representation of the current time in responseto detecting the first rotation comprises displaying the firstcurrent-time indicator in a different position on the display than aposition at which it was displayed prior to detecting the firstrotation.
 26. The method of claim 25, wherein updating the first userinterface to include the representation of the current time in responseto detecting the first rotation comprises animating the firstcurrent-time indicator from its initial position to the differentposition on the display.
 27. The method of claim 17, wherein thenon-current-time indicator is displayed at a location at which the firstcurrent-time indicator was displayed before the detection of the firstrotation of the physical rotatable input mechanism.
 28. The method ofclaim 17, further comprising: in response to detecting the firstrotation of the physical rotatable input mechanism relative to thehousing of the device, updating the first user interface to include atime difference indicator indicating a time difference between thecurrent time and the first non-current time.
 29. The method of claim 17,thither comprising: in response to a passage of time, update thenon-current-time indicator to indicate a second non-current time inaccordance with the passage of time, such that a time difference betweenthe current time and a presently indicated non-current time remainsfixed.
 30. The method of claim 17, further comprising: detecting asecond rotation of the physical rotatable input mechanism relative tothe housing of the device; in response to detecting the second rotationof the physical rotatable input mechanism, updating the first userinterface to include: the non-current-time indicator updated to indicatea third non-current time determined in accordance with the secondrotation; information corresponding to the third non-current timedisplayed at a location at which the first user interface object wasdisplayed prior to detecting the second rotation, wherein theinformation corresponding to the third non-current time pertains to thefirst information source and is information other than a day, time, ordate of the first non-current time; and the representation of thecurrent time.
 31. The method of claim 17, wherein displaying the firstuser interface on the display includes concurrently displaying: thefirst current-time indicator indicating a current time; the first userinterface object configured to display information corresponding to thecurrent time; and a second user interface object configured to displaysecond information corresponding to the current time, wherein the secondinformation corresponding to the current time pertains to a secondinformation source and is information other than a day, time, or date ofthe current time; and wherein the method further comprises: in responseto detecting the first rotation of the physical rotatable inputmechanism, update the first user interface to include: secondinformation corresponding to the first non-current time displayed at alocation at which the second user interface object was displayed priorto detecting the first rotation, wherein the second informationcorresponding to the first non-current time pertains to the secondinformation source and is information other than a day, time; or date ofthe first non-current time.
 32. The method of claim 31, wherein thefirst and second information sources are separate applications.
 33. Adevice comprising: a display; a physical rotatable input mechanism thatrotates relative to a housing of the device; one or more processors; andmemory storing instructions that, when executed by the one or moreprocessors, cause the device to: display a first user interface on thedisplay that includes concurrently displaying: a first current-timeindicator indicating a current time; and a first user interface objectconfigured to display information corresponding to the current time,wherein the information corresponding to the current time pertains to afirst information source and is information other than a day, time, ordate of the current time; while displaying the first user interface onthe display, detect a first rotation of the physical rotatable inputmechanism relative to the housing of the device; in response todetecting the first rotation of the physical rotatable input mechanism,update the first user interface to include: a non-current-tune indicatorindicating a first non-current time determined in accordance with thefirst rotation; information corresponding to the first non-current timedisplayed at a location at which the first user interface object wasdisplayed prior to detecting the first rotation, wherein the informationcorresponding to the first non-current time pertains to the firstinformation source and is information other than a day, time, or date ofthe first non-current time; and a representation of the current time,wherein the representation of the current time indicates the currenttime; while displaying the updated first user interface, detect a firsttouch contact on the display; and in response to detecting the firsttouch contact on the display: in accordance with a determination thatthe first touch contact is at a location corresponding to theinformation corresponding to the first non-current time displayed at alocation at which the first user interface object was displayed prior todetecting the first rotation: display a second user interfacecorresponding to the first user interface object, wherein the seconduser interface is based at least in part on the informationcorresponding to the first non-current time; and in accordance with adetermination that the first touch contact is at a locationcorresponding to the representation of the current time that isdisplayed concurrently with the non-current time indicator that wasdisplayed in response to detecting the first rotation of the physicalrotatable input mechanism, update the first user interface to: cease todisplay the non-current-time indicator that was displayed in response todetecting the first rotation of the physical rotatable input mechanism;and display information corresponding to the current time at a locationat which the first user interface object was displayed prior todetecting the first rotation.
 34. The device of claim 33, wherein theinstructions further cause the device to: in response to detecting thefirst rotation of the physical rotatable input mechanism relative to thehousing of the device, update the first user interface to indicate alack of information corresponding to the first non-current time.
 35. Thedevice of claim 33, wherein the first non-current time is a future time.36. The device of claim 35, wherein the information corresponding to thefirst non-current time comprises projected data.
 37. The device of claim35, wherein the information corresponding to the first non-current timecomprises a scheduled event.
 38. The device of claim 33, wherein thefirst non-current time is a past time.
 39. The device of claim 38,wherein the information corresponding to the first non-current timecomprises historical data.
 40. The device of claim 33, wherein updatingthe first user interface to include the representation of the currenttime in response to detecting the first rotation comprises displayingthe first current-time indicator with a modified visual appearance. 41.The device of claim 33, wherein updating the first user interface toinclude the representation of the current time in response to detectingthe first rotation comprises displaying the first current-time indicatorin a different position on the display than a position at which it wasdisplayed prior to detecting the first rotation.
 42. The device of claim41, wherein updating the first user interface to include therepresentation of the current time in response to detecting the firstrotation comprises animating the first current-time indicator from itsinitial position to the different position on the display.
 43. Thedevice of claim 33, wherein the non-current-time indicator is displayedat a location at which the first current-time indicator was displayedbefore the detection of the first rotation of the physical rotatableinput mechanism.
 44. The device of claim 33, wherein the instructionsfurther cause the device to: in response to detecting the first rotationof the physical rotatable input mechanism relative to the housing of thedevice, update the first user interface to include a time differenceindicator indicating a time difference between the current time and thefirst non-current time.
 45. The device of claim 33, wherein theinstructions further cause the device to: in response to a passage oftime, update the non-current-time indicator to indicate a secondnon-current time in accordance with the passage of time, such that atime difference between the current time and a presently indicatednon-current time remains fixed.
 46. The device of claim 33, wherein theinstructions further cause the device to: detect a second rotation ofthe physical rotatable input mechanism relative to the housing of thedevice; in response to detecting the second rotation of the physicalrotatable input mechanism, update the first user interface to include:the non-current-time indicator updated to indicate a third non-currenttime determined in accordance with the second rotation; informationcorresponding to the third non-current time displayed at a location atwhich the first user interface object was displayed prior to detectingthe second rotation, wherein the information corresponding to the thirdnon-current time pertains to the first information source and isinformation other than a day, time, or date of the first non-currenttime; and the representation of the current time.
 47. The device ofclaim 33, wherein displaying the first user interface on the displayincludes concurrently displaying: the first current-time indicatorindicating a current tune; the first user interface object configured todisplay information corresponding to the current time; and a second userinterface object configured to display second information correspondingto the current time, wherein the second information corresponding to thecurrent time pertains to a second information source and is informationother than a day, time, or date of the current time; and wherein theinstructions further cause the device to: in response to detecting thefirst rotation of the physical rotatable input mechanism, update thefirst user interface to include: second information corresponding to thefirst non-current time displayed at a location at which the second userinterface object was displayed prior to detecting the first rotation,wherein the second information corresponding to the first non-currenttime pertains to the second information source and is information otherthan a day, time, or date of the first non-current time.
 48. The deviceof claim 47, wherein the first and second information sources areseparate applications.